Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!milton!sumax!amc-gw!morpho!azar
From: azar@morpho.UUCP (Jim Van Horn)
Newsgroups: comp.sys.3b1
Subject: Re: csh
Keywords: ksh csh rc
Message-ID: <486@morpho.UUCP>
Date: 11 Mar 91 17:00:58 GMT
References: <5964@amc-gw.amc.com> <1991Mar7.043142.9412@blilly.UUCP> <1991Mar8.223519.25569@daffy.cs.wisc.edu> <2078@public.BTR.COM>
Reply-To: azar@apart.UUCP (Jim Van Horn)
Distribution: usa
Organization: North American Morpho Systems Inc, Tacoma WA
Lines: 20

I've used csh for some years.  Now I'm getting pretty comfortable
with ksh too.  One thing that I think csh does better is the
"last argument of the previous command" abbreviation (!$ on csh,
$_ on ksh).  I don't know why, but ksh saves the literal "$_" key
sequence in the history file instead of the substitution.
Incredibly dumb.

BTW, anyone tried the new shell on the block, rc?  From what little
I've read about it, it sounds attractive in that it's small and 
compact without losing a lot of functionality.  It's got its own
programming syntax, of course, but I don't write many shell scripts
anyway.  It does save commands in a history file, but there is no
history accessing mechanism.  You get to roll your own or wait for
the myriad packages to appear on the net.
-- 
	-=-	=-=	-=-	=-=	-=-	=-=	-=-
-Jim Van Horn	uunet!amc-gw!morpho!azar

	      "Where it falls mandrakes grow.
	That's why they shriek when you pull them up"