Re: Bug#9813: rxvt 2.20-4 : Bad setting of TERM environ variable
On May 16, J.H.M.Dassen wrote
> On May 15, John Goerzen wrote
> > Brian Mays <email@example.com> writes:
> > > rxvt (and rxvt-xpm) always exports the variable "COLORTERM" so that
> > > programs can check for color support. As a side note, when XPM support
> > > has been
> > Unfortunately, I know of no programs that make use of this variable. In
> > fact, I believe that ncurses doesn't even use it.
> The S-Lang library support it. For a demonstration: start up rxvt (I've used
> 2.20-4) and fire up mutt. You'll have colour support, with $TERM == xterm .
> Now start it up "env -u COLORTERM mutt". It'll be black&white.
Which makes for a very confusing setup, as COLORTERM doesn't get
propagated by telnet, ssh, etc. It took us a while to figure out under
what circumstances we got color.
What problem is COLORTERM trying to solve? It's very non-standard.
Also, I'd hope that if xterm now does color as standard, that fact is
reflected in its terminfo entry.
Bart Schuller firstname.lastname@example.org At Lunalabs, where the
Lunatech Research http://www.lunatech.com/ future is made today..
Partner of The Perl Institute http://www.perl.org/ Linux http://www.li.org/
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
email@example.com . Trouble?
e-mail to firstname.lastname@example.org .