Re: [9fans] tab completion and command history in rc

Re: [9fans] tab completion and command history in rc

[YAMANASHI Takeshi]

> 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 will
appear in the other output pane.

In acme, you could achieve similar effect by typing commands in a directory
window and the output appears in another "+Errors" window, but it's tiresome
to Button-2'ing the command everytime.
-- 
"on travel, off the network ... and a fossil in my pocket"

Re: [9fans] tab completion and command history in rc

[Russ Cox]

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 will
> appear in the other output pane.
>
> In acme, you could achieve similar effect by typing commands in a directory
> window and the output appears in another "+Errors" window, but it's tiresome
> to Button-2'ing the command everytime.

I do this in acme a lot.  Type a command, ESC, b2 click.

Russ

Re: [9fans] command history in rc

[kim kubik]

"YAMANASHI Takeshi"  wrote in message
> > As for command history, you are expected to
> > find the previous command in your rc window, edit it, copy it, paste it

> 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
will
> appear in the other output pane.

Is this something like your old pet? :

http://www.deinprogramm.de/scheme-2005/05-knauel/05-knauel.pdf

  - kim

Re: [9fans] command history in rc

[YAMANASHI Takeshi]

> Is this something like your old pet? :
> 
> http://www.deinprogramm.de/scheme-2005/05-knauel/05-knauel.pdf

Almost yes except that it's using ncurses.
I'd rather use mouse. :)
# wait, linux terminal has supported the mouse?
-- 

Re: [9fans] command history in rc

[David Leimbach]

On 11/7/05, YAMANASHI Takeshi <9.nashi@gmail.com> wrote:
> > Is this something like your old pet? :
> >
> > http://www.deinprogramm.de/scheme-2005/05-knauel/05-knauel.pdf
>
> Almost yes except that it's using ncurses.
> I'd rather use mouse. :)
> # wait, linux terminal has supported the mouse?

Yep, you've been able to highlight stuff in linux for copy/paste for
at least the last 6 or 7 years that I've been doing it.

I do that on FreeBSD too.

But mainly between virtual terminals... I don't start X unless I'm
really needing multiple visible windows on the screen that I need to
move around at once.

> --
>
>
>