9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] History
Date: Thu,  9 Nov 2000 16:39:29 +0000	[thread overview]
Message-ID: <20001109163657.A5BC2199E6@mail.cse.psu.edu> (raw)

if you are intent for whatever reason on capturing, recovering, and
especially modifying typed input on the fly (as with command
completion but other things as well), i'd plug something (cf. pipefile)
between typist and the recipient of the typing.  it could keep as much
history as desired, make the contents available as a real or virtual
file, and generally do what it liked.  putting the facility in the
shell alone seems to assume that's the only thing that would ever
benefit (which probably explains why so many other applications on gnunix
include readline, so lots-but-not-all typed-at commands get it, not just bash).
since the typed-editing-history facility is used interactively, would
tend to me to suggest that it belongs (only) along a path of interaction.
there are several points where that could be done, depending on the desired
scale of memory.



             reply	other threads:[~2000-11-09 16:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 16:39 forsyth [this message]
2000-11-10  9:35 ` Douglas A. Gwyn
2000-11-14  9:33   ` George Michaelson
2000-11-14  9:51     ` Boyd Roberts
2000-11-14 15:50       ` Douglas A. Gwyn
2000-11-14 16:13         ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2006-07-07 15:21 [9fans] history Fco. J. Ballesteros
2006-07-07 16:16 ` Skip Tavakkolian
2002-01-22 20:43 rob pike
2000-11-14 21:39 [9fans] History presotto
2000-11-14 21:46 ` Boyd Roberts
2000-11-14 20:45 Richard Miller
2000-11-14 19:12 anothy
2000-11-14 19:37 ` Boyd Roberts
2000-11-14 17:21 rog
2000-11-14 14:28 rob pike
2000-11-14 15:12 ` Boyd Roberts
2000-11-09 18:34 rob pike
2000-11-09 16:15 rog
2000-11-09 15:26 ` Boyd Roberts
2000-11-09 14:01 rob pike
2000-11-09 14:50 ` Boyd Roberts
2000-11-09 15:20   ` Axel Belinfante

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=20001109163657.A5BC2199E6@mail.cse.psu.edu \
    --to=forsyth@vitanuova.com \
    --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).