So Linux policy is to support only terminals that generate ^? for
backspace? I thought Unix-like systems were supposed to be usable from a
great variety of text terminals. Debian's policy works when your universe
consists solely of Linux machines configured to Debian specifications,
where your terminals are just the Linux console, xterm and screen,
but it fails to handle glass ttys, or xterms running on other systems.
I recall the reaction when someone proposed changing zsh's line editor
(ZLE) to treat backspace and delete characters differently. Just among
the developers we have users of a wide variety of terminals, and the
proposed change would have broken the line editor for many of us.
As it is, ZLE just works, with no extra effort, on any text terminal,
and we get no complaints.
> Original telnet has
>IAC sequences to send a "delete" regardless of keymapping policies that
>are not known at end points.
Yes, it was a nice model, a pity it fell out of use. Telnet defined a
Network Virtual Terminal, that was intended to be a common terminal type
to be emulated on all Telnet sessions, which would have eliminated the
need for the server to know what terminal type was being used on the
client end. Of course, the NVT was a product of its time: no cursor
addressing, no display attributes, and on the input side only a single
erase key. The closest equivalent to this model that is currently in
use is the de facto almost-universal capability to emulate a VT100.
These days telnet connections (and rsh and ssh) are used more as dumb
pipes to talk to the user's actual terminal. We can't change that,
and the result is that Unix systems have to handle whatever terminal
type the user is using.
-zefram
-
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/