Article View: gnu.bash.bug
Article #614Re: 1.03 comments
From: Bennett Todd
Date: Mon, 18 Sep 1989 21:41
Date: Mon, 18 Sep 1989 21:41
11 lines
895 bytes
895 bytes
>Each line of a loop is put into the history separately, so you can't do >!for. Sure you can -- you'll just get the "for" starter. I sure appreciate this -- I *love* composing many-line-long loops interactively, and the ability to go back and snatch lines from out of a previous loop construction makes it wonderful to do slightly different loops, or to resubmit a loop with an internal typo corrected. The approach taken to adding loops to history is one of my favorite bash features. -Bennett bet@orion.mc.duke.edu
Technical Details
Message-ID:
<8909182141.AA09026@orion>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!orion.mc.duke.edu!betShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!orion.mc.duke.edu!bet From: bet@orion.mc.duke.edu (Bennett Todd) Newsgroups: gnu.bash.bug Subject: Re: 1.03 comments Message-ID: <8909182141.AA09026@orion> Date: 18 Sep 89 21:41:46 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 11