public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Chris Adams <cmadams@hiwaay.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REVERT Request] VT Breakage
Date: Tue, 14 Oct 2008 15:17:33 -0700	[thread overview]
Message-ID: <48F51A7D.3040700@zytor.com> (raw)
In-Reply-To: <20081014213820.GA1312840@hiwaay.net>

Chris Adams wrote:
> Once upon a time, H. Peter Anvin <hpa@zytor.com> said:
>> VT220 was monochrome, too.  You needed to go to the VT241 before you got 
>> color in the DEC terminal range (and even it didn't support color text 
>> via the SGR sequence (CSI m), according to the manual -- even the VT510 
>> manual doesn't document colored text via SGR.)
> 
> The VT510 is also monochrome (I'm sitting here typing on one).

Indeed it is.  The color version is the VT525.

I haven't found the technical manual for VT525, but the user manual 
mentions as one of options in the configuration menu:

"Erase text to the text background color (PC style)"
"Erase text to the screen background color (VT style)"

However, to a very large degree this is all moot.  We have done it one 
way for 17 years, and that is the terminal emulation that is expected 
when $TERM is "linux".  Realistically, if we want to introduce a new 
xterm-compatible mode it needs to be just that, a mode; and then we can 
set TERM to "xterm".

	-hpa

  reply	other threads:[~2008-10-14 22:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 10:56 [REVERT Request] VT Breakage Alan Cox
2008-10-14 16:59 ` Linus Torvalds
2008-10-14 17:30   ` Alan Cox
2008-10-14 17:49     ` H. Peter Anvin
2008-10-14 21:38       ` Chris Adams
2008-10-14 22:17         ` H. Peter Anvin [this message]
2008-10-14 22:29           ` H. Peter Anvin
     [not found] <bmPNn-6ta-11@gated-at.bofh.it>
     [not found] ` <bmVzl-5F8-13@gated-at.bofh.it>

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=48F51A7D.3040700@zytor.com \
    --to=hpa@zytor.com \
    --cc=cmadams@hiwaay.net \
    --cc=linux-kernel@vger.kernel.org \
    /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