Howard Chu wrote:
quoted text
> Andi Kleen wrote:
>> e.g. history management is definitely something that should not
>> be done in the kernel.

I must be going senile or something. You're absolutely right of course. I just 
dug up my old telnet patches from 1989 that implemented the command history in 
the client. All that we need today is a patch for GNU readline that makes it 
mostly do nothing when EXTPROC mode is set on the tty.

We still need to be able to forward on <TAB> of course. We can define 
additional forwarding characters using VEOL or VEOL2, but I think they also 
have the semantic of terminating the input line, which is not what we want 
here. Since they are so rarely used for their original purpose, would it be a 
terrible thing to subvert them to this purpose, or can we just add a new VFWD 
character to the tty driver?

quoted text
> I definitely wasn't trying to suggest that the management occur in the kernel.
> Only that some mechanism for telling the client to toggle the feature on or
> off would be useful.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/