From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] History
From: forsyth@vitanuova.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20001109163657.A5BC2199E6@mail.cse.psu.edu>
Date: Thu,  9 Nov 2000 16:39:29 +0000
Topicbox-Message-UUID: 25ecf864-eac9-11e9-9e20-41e7f4b1d025

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.