I've just found a link to this ancient bugreport in
https://en.wikipedia.org/wiki/ANSI_escape_code.
Unfortunately this discussion here contains two confusing mistakes. I'd
like to correct them for future reference purposes. No action necessary,
other than perhaps closing this bug, and fixing the
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1429584
Title:
gnome-terminal doesn't set
Can we make it so the new VTE release appear in Ubuntu 15.04 ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1429584
Title:
gnome-terminal doesn't set $COLORTERM from 3.14
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-terminal (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
In https://github.com/GNOME/gnome-
terminal/commit/1d5c1b6ca6373c1301494edbc9e43c3e6a9c9aaf I've found that
you're most worried how you'll set TERM=xterm-256color.
As pointed out in the links above, checking for $VTE_VERSION could be
one approach.
Note that vte-0.40 (gnome-terminal-3.16) will
This affects release: Vivid Vervet
How exactly does it effect it?
$COLORTERM was dropped for a good reason; appart from the links you
posted the best explanation is probably at
https://bugzilla.gnome.org/show_bug.cgi?id=733423.
$COLORTERM should not be necessary ever. Instead of bringing it
This flag is used to 'upgrade' from xterm to xterm-256color in almost
every bash environment people use...
$VTE_VERSION will also be dropped from version 3.15 onwards:
https://github.com/GNOME/gnome-
terminal/commit/71de106ca360854d63739a015278452085eeb19b
--
You received this bug notification
This flag is used to 'upgrade' from xterm to xterm-256color in almost
every bash environment people use...
Then these should be fixed.
COLORTERM's semantics have nothing to do with 256 color support per se,
it was a mere coincidence that all terminals that set this variable also
supported 256
** Description changed:
Gnome terminal has dropped the $COLORTERM workaround for invalid
terminfo/termcap.
References:
https://github.com/GNOME/gnome-terminal/commit/1d5c1b6ca6373c1301494edbc9e43c3e6a9c9aaf
https://bugzilla.redhat.com/show_bug.cgi?id=1165439
