Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!amdahl!pacbell!unet!rodc
From: rodc@unet.unet.pacbell.COM (Rod Creason)
Newsgroups: comp.unix.wizards
Subject: Re: Thank you, Bill Joy!
Keywords: csh ksh
Message-ID: <43@unet.unet.pacbell.COM>
Date: 1 Sep 88 15:18:53 GMT
References: <2323@munnari.oz> <2662@uvacs.CS.VIRGINIA.EDU>
Reply-To: rodc@unet.PacBell.COM (Rod Creason)
Organization: Network Equipment Technologies, Redwood City, CA
Lines: 20

In article <2662@uvacs.CS.VIRGINIA.EDU> rwl@uvacs.CS.VIRGINIA.EDU (Ray Lubinsky) writes:
>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.

I agree completely.  I used csh for many years until I was without and
had to use ksh.  Now that I have used the korn shell I will only use csh
when I must (at work we do not have ksh).  The editing capabilities are
wonderful (it even supports 'undo').


-------------
Rod Creason,                    uucp:      ...!{ames,amdahl,pacbell}!unet!rodc
Advanced Development,           
Network Equipment Technologies