From: kim kubik <chaotrope@jps.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] command history in rc
Date: Mon, 7 Nov 2005 09:38:43 +0000 [thread overview]
Message-ID: <0hdbf.214$c_1.95@newsread3.news.pas.earthlink.net> (raw)
In-Reply-To: <0044f392abc1f0419e4121eaee8519fa@orthanc.cc.titech.ac.jp>
"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
next prev parent reply other threads:[~2005-11-07 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 2:30 [9fans] tab completion and " YAMANASHI Takeshi
2005-11-04 3:08 ` Russ Cox
2005-11-07 9:38 ` kim kubik [this message]
2005-11-08 5:21 [9fans] " YAMANASHI Takeshi
2005-11-08 15:31 ` David Leimbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0hdbf.214$c_1.95@newsread3.news.pas.earthlink.net' \
--to=chaotrope@jps.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).