Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!mailrus!uflorida!haven!uvaarpa!virginia!uvacs!rwl
From: rwl@uvacs.CS.VIRGINIA.EDU (Ray Lubinsky)
Newsgroups: comp.unix.wizards
Subject: Re: Thank you, Bill Joy!
Message-ID: <2662@uvacs.CS.VIRGINIA.EDU>
Date: 1 Sep 88 00:47:06 GMT
References: <2323@munnari.oz>
Organization: U.Va. CS in Charlottesville VA
Lines: 28

In article <2323@munnari.oz>, kre@munnari.oz (Robert Elz) writes:
> What is needed is a way to do
> 
> 	ls /a >/tmp/file
> 	ls /b | comm - !$
> or
> 	echo old*
> 	rm !$
> 
> neither of which will do anything like what you want if you replace
> csh with ksh and !$ with $_

Jeez!  Use the bleeding edit mode in Korn shell!

Using vi-style command line editing I can modify previous commands like you've
shown in at least the amount of time you can do it with csh's !$ construct AND
I get the visual reassurance of seeing what the newly-edited command is really
going to be.

Csh history editing mechanism is a pitiful kludge compared to actually EDITING
your past commands.  (I cut my teeth on csh so its not that I haven't seen
both sides of the UNIX shell fence.)  Hunt-and-peck typists need not apply.

-- 
| Ray Lubinsky,                    UUCP:      ...!uunet!virginia!uvacs!rwl    |
| Department of                    BITNET:    rwl8y@virginia                  |
| Computer Science,                CSNET:     rwl@cs.virginia.edu  -OR-       |
| University of Virginia                      rwl%uvacs@uvaarpa.virginia.edu  |