Mark Eichin <[EMAIL PROTECTED]> writes:
> in practice, the "linux" entry not being supported by solaris (for
> example) was handled by people doing "set term=vt100" and whining a
> lot...
A solution is to tell them to:
linux$ infocmp xterm-color > missing-term.tic
(replace `xterm-color' with
in practice, the "linux" entry not being supported by solaris (for
example) was handled by people doing "set term=vt100" and whining a
lot...
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
On Jun 22, Mark Eichin wrote
> Except that the xterm-color entry isn't particularly widespread, yet;
> so if you rlogin or telnet somewhere that doesn't have it, you pretty
> much lose.
termcap supported the TERMCAP environmental variable, which solved
problems like this (and like "linux" not bei
Except that the xterm-color entry isn't particularly widespread, yet;
so if you rlogin or telnet somewhere that doesn't have it, you pretty
much lose. This is the main reason I'm reluctant to force the
change... though I might be convinced to do it for the unstable (with
libc6 and all the other ex
I have a question about the terminfo entry for 'xterm' I am wondering
how I need to adjust it so that it says color is supported. xterm now
supports color (demonstrated by ls --color and tin in color), but the
terminfo entry still says black and white so programs like lynx and
slrn are blackand w
5 matches
Mail list logo
