public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Antonino A. Daplas" <adaplas@pol.net>
Subject: Re: [REVERT Request] VT Breakage
Date: Tue, 14 Oct 2008 10:49:23 -0700	[thread overview]
Message-ID: <48F4DBA3.4060907@zytor.com> (raw)
In-Reply-To: <20081014183002.059237e7@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> So please check this patch. Also, can somebody please verify what the 
>> _correct_ vt100 behavior is? The test-case was in the original commit, but 
> 
> Ahah a trick question - VT100 is monochrome. Colour VT as far as I can
> tell (and while I have a genuine VT220 I don't have a non-clone colour
> terminal[1]) behaves as we did *before* this changeset.
> 
> Alan
> [1] And nobody send me one or Telsa will kill me

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.)

MS-DOS ANSI.SYS definitely only had one attribute at any time; new lines 
was filled in with the current attribute.

	-hpa

  reply	other threads:[~2008-10-14 17:50 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 [this message]
2008-10-14 21:38       ` Chris Adams
2008-10-14 22:17         ` H. Peter Anvin
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=48F4DBA3.4060907@zytor.com \
    --to=hpa@zytor.com \
    --cc=adaplas@pol.net \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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