[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Probable mistake in vte-256color
From: |
Thomas Dickey |
Subject: |
Re: Probable mistake in vte-256color |
Date: |
Sat, 16 Jan 2016 18:23:09 -0500 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, Jan 12, 2016 at 05:38:18PM +0100, Leonardo Brondani Schenkel wrote:
> This is the definition for vte-256color:
>
> # palette is hardcoded...
> vte-256color|VTE with xterm 256-colors,
> use=xterm+256color, use=vte,
>
> However, all other definitions in terminfo.src with the same "palette is
> hardcoded" comment inherit from "xterm+256setaf" and *not*
> "xterm+256color" as listed above. I believe that "use=xterm+256setaf"
> was the intent and the above definition is incorrect.
no... I think I overlooked the comment. That particular line dates from
2007. There was an interval of several years between various terminal
developers announcing "xterm 256colors" and getting around to implementing
the escape sequence to update the palette (and oddly enough, generally
not mentioning this in their release notes or change history except in
the most obscure terms). For VTE, it seems this was addressed in 2009
according to my note:
# 2012-11-02
# * reviewed vte-2012, reverted most of the change since it was incorrect
# based on testing with tack -TD
# * un-cancel the initc in vte-256color, since this was implemented
# starting with version 0.20 in 2009 -TD
In a quick check,
PuTTY 0.62 is hardcoded
Konsole 15.08.0 is hardcoded
mlterm implements the palette control (enough for terminfo anyway)
VTE (seen in gnome-terminal 3.18.2) works correctly.
--
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature