Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!gatech!rayssd!galaxia!dave
From: dave@galaxia.Newport.RI.US (David H. Brierley)
Newsgroups: comp.sources.d
Subject: Re: Bourne Again Shell?
Message-ID: <544@galaxia.Newport.RI.US>
Date: 18 Feb 89 03:35:03 GMT
References: <26563@teknowledge-vaxc.ARPA> <46100006@hcx3> <1491@vicom.COM>
Reply-To: dave@galaxia.Newport.RI.US (David H. Brierley)
Organization: Dave's Very Own Personal System
Lines: 22

In article <1491@vicom.COM> lmb@vicom.COM (Larry Blair) writes:
>
>I'm not saying that there aren't things lacking in ksh; I miss "!! newstuff"
>and "!*" would be really useful.  It's just nice to only have to deal with
>one editor syntax.

For the "!! newstuff" try using "<ESC>kA newstuff".  I dont see where the
problem is with the "!*" syntax, just pull back the last command and edit
the first word.  I think the most useful thing for someone who wants to
make the most of the history mechanism in the ksh is if they have a very
thorough understanding of vi.  I suppose a thorough understanding of emacs
would allow you to make efficient use of emacs mode as well.

I would like to see a csh user show me how to achieve the following using
the csh history mechanism: retrieve the third previous command that contains
the string "foo" and then change the fourth word on the line to the word
"bar".  In ksh: "<ESC>/foo<CR>nn3Wcwbar<CR>".  Like I said, a knowledge of
vi is extremely helpful.
-- 
David H. Brierley
Home: dave@galaxia.Newport.RI.US   {rayssd,xanth,lazlo,jclyde}!galaxia!dave
Work: dhb@rayssd.ray.com           {sun,decuac,gatech,necntc,ukma}!rayssd!dhb