You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's needed for eg. automatically spawning instance of tmux (which i don't want to do in gnome-terminal/Terminal)
Couple of terminals that sets COLORTERM — gnome-terminal, Terminal, rxvt-xpm
One that doesn't — terminology
Most of those which are running under X11 are using xterm-256color terminfo/termcap, so there was a need to differentiate them from the shell script in this way ;)
The text was updated successfully, but these errors were encountered:
Uh, yeah, we should probably set some environment variable. But to be honest, I am not 100% sure what COLORTERM is used for if TERM is set to something different. Applications might check this and as long as we don't ship a kmscon terminfo/termcap file, I don't think we should set this.
I will think about it, but some more investigation is definitely needed.
Thanks!
TERM is for terminfo/termcap and COLORTERM is for real name of the terminal (usually). It's used because almost every terminal emulator is using xterm-256color terminfo. Not all terminal emulators are setting COLORTERM (eg. terminology, but it's quite a fresh terminal emulator)
I had to make /bin/login preserve the environment to actually pass COLORTERM through, but this is now possible. See commit 6be24df This should fix the issue.
One of the widely used ones is $COLORTERM
It's needed for eg. automatically spawning instance of tmux (which i don't want to do in gnome-terminal/Terminal)
Couple of terminals that sets COLORTERM — gnome-terminal, Terminal, rxvt-xpm
One that doesn't — terminology
Most of those which are running under X11 are using xterm-256color terminfo/termcap, so there was a need to differentiate them from the shell script in this way ;)
The text was updated successfully, but these errors were encountered: