Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!osu-cis!att!chinet!mcdchg!nud!fishpond!fnf From: fnf@fishpond.UUCP (Fred Fish) Newsgroups: comp.unix.wizards Subject: Re: Thank you, Bill Joy! Message-ID: <124@fishpond.UUCP> Date: 27 Aug 88 19:50:27 GMT References: <65@volition.dec.com> <2402@rtech.rtech.com> <2323@munnari.oz> Reply-To: fnf@fishpond.UUCP (Fred Fish) Organization: occasionally Lines: 50 In article <2323@munnari.oz> kre@munnari.oz (Robert Elz) writes: >It is an important one, but !$ is just as important. I have never used >a BRL sh, but ksh's $_ (while useful itself sometimes), just doesn't come >close. > [Examples of use of csh !$ deleted -fnf] >neither of which will do anything like what you want if you replace >csh with ksh and !$ with $_ Are you confusing <_> with <.> ? As far as I can tell, and I'm not a csh user, the ksh <.> sequence does exactly what the csh !$ mechanism does, except that ksh echos the line to be executed before you hit CR, while csh echoes it afterwards: Script started on Sat Aug 27 12:40:06 1988 fishpond:1574> csh % echo a b c a b c % echo !$ echo c c % ls /x/usr/fnf/bin/* /x/usr/fnf/bin/OLDbru /x/usr/fnf/bin/analyze /x/usr/fnf/bin/beep % ls !$ ls /x/usr/fnf/bin/* /x/usr/fnf/bin/OLDbru /x/usr/fnf/bin/analyze /x/usr/fnf/bin/beep % exit fishpond:1575> ksh fishpond:1576> echo a b c a b c fishpond:1577> echo c (I actually typed "echo <.>") c fishpond:1579> ls /x/usr/fnf/bin/* /x/usr/fnf/bin/OLDbru /x/usr/fnf/bin/analyze /x/usr/fnf/bin/beep fishpond:1580> ls /x/usr/fnf/bin/* (I actually typed "ls <.>") /x/usr/fnf/bin/OLDbru /x/usr/fnf/bin/analyze /x/usr/fnf/bin/beep fishpond:1581> exit fishpond:1583> exit script done on Sat Aug 27 12:42:05 1988 -- # Fred Fish, 1346 West 10th Place, Tempe, AZ 85281, USA # noao!nud!fishpond!fnf (602) 921-1113