28 Jun
2016
28 Jun
'16
3:29 a.m.
On Mon, Jun 27, 2016, at 16:33, Ronald Natalie wrote:
Command line editing might have been implemented in
the driver as
enhanced editing in “cooked” mode, but the history
is a bit more context specific.
MS Windows does a kind of halfway decent job of this by having a
separate history per program, which I don't think requires any
information the terminal driver doesn't have access to (the process that
is trying to read from the terminal, and the binary running in that
process)