Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox
From: bfox@AUREL.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Some minor bash nits/wouldlikes
Message-ID: <8909021449.AA14827@aurel.caltech.edu>
Date: 2 Sep 89 14:49:00 GMT
References: <197@titania.warwick.ac.uk>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.caltech.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 29


   Date: 2 Sep 89 12:45:18 GMT
   From: mcsun!ukc!warwick!cudcv@uunet.uu.net  (Rob McMahon)
   Organization: Computing Services, Warwick University, UK
   References: <8909010622.AA04478@baby.bby.oz>, <8909011533.AA11301@aurel.caltech.edu>
   Sender: bug-bash-request@prep.ai.mit.edu

   In article <8909011533.AA11301@aurel.caltech.edu> bfox@aurel.caltech.edu writes:
   >THe ampersand is replaced by the matched text?  What if you are just adding
   >an ampersand, which seems to me to be a common case:
   >
   >	bash$ hairy-function argument
   >	bash$ !!:s/argument/another-argument &	<- user wants to background this job.

	   bash$ !!:s/argument/another-argument/ &
   or
	   bash$ !!:s/argument/another-argument \&
   or even
	   bash$ !!:s/argument/another-&/ &
   :-)

   This is very useful sometimes for small additions to long replacements.

How about:

bash$ hairy-function argument
bash$ ^ar^another-ar^ &

Brian