From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Thu, 3 Nov 2005 22:08:25 -0500 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] tab completion and command history in rc In-Reply-To: <0044f392abc1f0419e4121eaee8519fa@orthanc.cc.titech.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <0044f392abc1f0419e4121eaee8519fa@orthanc.cc.titech.ac.jp> Topicbox-Message-UUID: a4f8d91e-ead0-11e9-9d60-3106f5b1d025 On 11/3/05, YAMANASHI Takeshi <9.nashi@gmail.com> wrote: > > As for command history, you are expected to > > find the previous command in your rc window, edit it, copy it, paste it > > to the prompt, and then run it. This is obviously more efficient than > > hitting the "up" arrow. > > As for keeping the command line always in view, mid-click on the window > > and select "scroll". > > This reminded me of my old pet idea. To ease finding the desired command > in a window, how's it to split the window into two panes like sam does? > I mean, you always enter commands in the command pane and every outputs w= ill > appear in the other output pane. > > In acme, you could achieve similar effect by typing commands in a directo= ry > window and the output appears in another "+Errors" window, but it's tires= ome > to Button-2'ing the command everytime. I do this in acme a lot. Type a command, ESC, b2 click. Russ