Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!hcx1!hcx3!shirono From: shirono@hcx3.SSD.HARRIS.COM Newsgroups: comp.sources.d Subject: Re: Bourne Again Shell? Message-ID: <46100006@hcx3> Date: 14 Feb 89 15:01:00 GMT References: <26563@teknowledge-vaxc.ARPA> Lines: 46 Nf-ID: #R:teknowledge-vaxc.ARPA:26563:hcx3:46100006:000:1885 Nf-From: hcx3.SSD.HARRIS.COM!shirono Feb 14 10:01:00 1989 In comp.sources.d, les@chinet.chi.il.us writes: > In article <3071@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: > >Korn Shell with CSH history... > >Is that too much to ask? > > I really hate to ask this, but... What can you do with csh history that > you can't do with ksh's? I really like the ksh ability to use editor > syntax to search for a previous command and modify it before re-execution. > Does csh have something like that? Ksh and csh have two different philosophies as far as command history editing goes. They both have good and bad points. What I miss from the csh is the ability to say: ``I want words 0 thru 5 and 7 thru 11.'' !:0-5 !:7-11 or ``I want everything exactly the same, but change the string `foo' for `bar' in the last word.'' !:0- !$:gs/foo/bar/ These changes might look trivial, but when your command line has wrapped around (or scrolled left) a few times it gets to be a drag. Even worse is ``I want to apply command `foo' to the last word of the previous command.'' foo !$ Note, I'm not saying these can't be done with ksh, but I'm saying that I'd rather write !$, however cryptic, than go through an unending sequence of keystrokes to accomplish the exact same thing. Perhaps having both would be the best. --Roberto ______________________________________________________________________________ || Internet: shirono@ssd.harris.com Roberto Shironoshita || Harris Corporation || ...!novavax---\ Computer Systems Division || UUCP: ...!uunet-------!hcx1!shirono || ...!mit-eddie-/ ------------------------------------------------------------------------------ DISCLAIMER: The opinions expressed here are my own; they in no way reflect the opinion or policies of Harris Corporation.