On Fri, 17 Jun 2005, [iso-8859-1] Frédéric Brière wrote:
On Fri, Jun 17, 2005 at 02:17:19PM -0400, Thomas Dickey wrote:
Perhaps because $TERM is set to "xterm" rather than "Eterm".
Guilty as charged. TERM=Eterm was a PITA when ssh'ing into old boxen
that didn't recognize it, so I got rid of it a long time ago.
I confirm that TERM=Eterm makes everything dandy again. (Plus, these
old boxen appear to have been upgraded, so I can get rid of that xterm
kludge.)
Given that Eterm aims to be xterm-compatible, does this mean this bug
report should be reassigned to it?
man Eterm
Eterm -- version 0.9.2 -- is a color vt102 terminal emulator intended
as an xterm(1) replacement. ...
man xterm
The xterm program is a terminal emulator for the X Window System. It
provides DEC VT102/VT220 (VTxxx) and Tektronix 4014 compatible termi-
nals for programs that cannot use the window system directly. ...
The particular feature in question is ISO-6429 (not VT220 per se).
Likewise color - it's not a feature of vt102/vt220. I should add that
to the first paragraph in xterm's manpage.
The wording from Eterm's manpage is adapted from rxvt's, which does not
really state that it is a full replacement for xterm. The main reason why
"xterm" (or "vt100", "ansi" or "linux") is used is as you observe, a
matter of convenience rather than accuracy.
The same (differing features) is true of several emulators. There's no
solution that appeals to everyone. I generally install local terminfo's
for the emulators that I use (aside from testing: xterm, PuTTY, Tera Term,
as well as screen, customized for those).
Usually I point out that none of the various emulators have the same
function-key definitions, though they have lots of those in common. That
doesn't seem to win many arguments (down in the noise level with things
like "vt100 colors").
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
