Article View: gnu.bash.bug
Article #367Incomplete history handling.
From: jkh
Date: Thu, 20 Jul 1989 16:08
Date: Thu, 20 Jul 1989 16:08
48 lines
1527 bytes
1527 bytes
Grumble. One of the things I really like about bash is that it's
*almost* csh compatible. I've grown far too used to !! and ^foo^bar
type constructs to go back to any sh-like shell at this point, so
bash's approach seems good (I've always written my scripts in bourne
shell, so that's not a problem). However, there are a few problems:
bash$ echo foo bar baz
foo bar baz
bash$ !!
echo foo bar baz
foo bar baz
bash$ !ec
echo foo bar baz
foo bar baz
bash$ !?foo?
echo foo bar baz
foo bar baz
bash$ !!:s/foo/feh
echo feh bar baz
feh bar baz
bash$ !ech:s/foo/feh
:s/foo/feh: Event not found.
The last case should work, if we're really looking for csh compatability.
Also, !..:gs/foo/bar does not work either (global substitute):
bash$ echo foo bar baz
foo bar baz
bash$ !!:gs/ba/bo
echo foo bar baz:gs/ba/bo
foo bar baz:gs/ba/bo
bash$
Definately not what the doctor ordered.
Jordan
--
--------
Jordan Hubbard
PCS Computer Systeme GmbH
West Germany
UUCP: {uunet,decwrl}!pyramid!pcsbst!jkh
ARPA: jkh@violet.berkeley.edu
Hey! Leave that alone!
Technical Details
Message-ID:
<933@pcsbst.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!mcvax!unido!pcsbst!jkhShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!mcvax!unido!pcsbst!jkh From: jkh@pcsbst.UUCP (jkh) Newsgroups: gnu.bash.bug Subject: Incomplete history handling. Message-ID: <933@pcsbst.UUCP> Date: 20 Jul 89 16:08:20 GMT Reply-To: jkh@meepmeep.pcs.com (Jordan K. Hubbard) Organization: PCS GmbH, Pfaelzer-Wald-Str. 36, 8000 Muenchen; West-Germany Lines: 48