From: Richard Uhtenwoldt <ru@ohio.river.org>
To: 9fans@cse.psu.edu
Subject: [9fans] command history
Date: Fri, 14 Jul 2000 14:25:11 -0700 [thread overview]
Message-ID: <200007142125.OAA07055@ohio.river.org> (raw)
In-Reply-To: <200007142103.OAA06763@ohio.river.org>
I just wrote:
> instead of rio invoking "rc", rio could invoke
>"ile;rc" where the only effect of the ile command is to bind /dev/cons
>to a fileserver which stores the commandline history and interprets the
>history-editing commands. that way, no modification to rc or rio would
>be needed: ile would "sit between" rio and rc.
ignore this. when I wrote this I did not consider that rio sends whole
lines to rc, not individual keystrokes.
next prev parent reply other threads:[~2000-07-14 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 14:16 Stephen C. Harris
2000-07-14 21:03 ` Richard Uhtenwoldt
2000-07-14 21:25 ` Richard Uhtenwoldt [this message]
2000-07-14 19:44 Russ Cox
2000-07-14 21:37 Russ Cox
2000-07-14 23:24 ` Richard
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=200007142125.OAA07055@ohio.river.org \
--to=ru@ohio.river.org \
--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).