linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zefram@fysh.org
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Re: [PATCH] tty canonical mode: nicer erase behaviour
Date: Sun, 23 Sep 2001 23:12:32 +0100	[thread overview]
Message-ID: <E15lHUG-0001N5-00@bowl.fysh.org> (raw)

Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>Your xterm is not following Linux policy - this is a solved problem in
>Linuxspace. Debian bit the bullet a few years ago and did the neccessary
>deed to make all their terminal emulators and console match.

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

             reply	other threads:[~2001-09-23 22:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-23 22:12 zefram [this message]
2001-09-24  0:03 ` [PATCH] tty canonical mode: nicer erase behaviour Alan Cox
2001-09-24  2:17   ` zefram
2001-09-24  5:19   ` [PATCH] Enable SSE on K7's with old/broken BIOS's John Clemens
2001-09-24 12:29     ` Alan Cox
2001-09-24  1:25 ` [PATCH] tty canonical mode: nicer erase behaviour Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2001-09-23 21:26 zefram
2001-09-23 21:48 ` Alan Cox
     [not found] <mailman.1001266380.13783.linux-kernel2news@redhat.com>
2001-09-23 18:12 ` Pete Zaitcev
2001-09-23  2:26 zefram
2001-09-23 20:05 ` Alan Cox
2001-09-23 20:41   ` Nadav Har'El
2001-09-23 21:50     ` Alan Cox
2001-09-24  9:22       ` Nadav Har'El
2001-09-23 22:57     ` Matthias Andree
2001-09-24  6:45 ` Kai Henningsen

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=E15lHUG-0001N5-00@bowl.fysh.org \
    --to=zefram@fysh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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).