Well, just because it is easy does not make it the right thing to
do. I am not an xterm developer, but I would question why xterm
would have to take one specific environment variable it to
account,
invented by another terminal emulator, to solve a potential
problem
in Emacs.
The problem can affect any program that looks at COLORTYPE.
It is not specific to Emacs. This change would make xterm work
correctly
with rxvt. Can you think of another way to do that?
IMHO, if rxvt has capabilities not in xterm, it should not set TERM
to xterm in the first place. If you set TERM to xterm you should not
expect programs to jump through hops trying to figure out if it
really is an xterm or rather something else. I would just say that
anybody expecting to get rxvt.el loaded
when TERM is set to xterm has a misconfigured system and leave it at
that. But that is just IMHO.
Jan D.
_______________________________________________
Emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
