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 default to TERM=xterm- 256color (commit 82a8b06). It might be the best move for Ubuntu to backport this patch to its current vte packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1429584 Title: gnome-terminal doesn't set $COLORTERM from 3.14 onwards Status in gnome-terminal package in Ubuntu: New Bug description: 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 https://bugzilla.redhat.com/show_bug.cgi?id=1173688 https://bugzilla.redhat.com/show_bug.cgi?id=1166428 This affects release: Vivid Vervet Workaround I currently use is `.bashrc`: if [ -z "$COLORTERM" ] && cat /proc/$PPID/exe 2> /dev/null | grep -q gnome-terminal; then export COLORTERM=gnome-terminal fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1429584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
