Subject: Re: xterm v. xterm-old
To: Julian Coleman <firstname.lastname@example.org>
From: M L Riechers <email@example.com>
Date: 02/05/2001 19:30:04
>> 1) Why is lynx completely useless with TERM=xterm (full-on blank
>> white). Will recompiling it fix this? (I doubt it, since I'm pretty
>> sure I built it *after* installing 1.5 and its new termcaps on this
> This I don't understand. Can you send me the lynx screen output please
> (something like `lynx > lynx.out`, then type 'q' and 'y')? I might be
> able to work out what's happening here.
Me, too, although with us it's a case of the background turning a
bright chartreuse (-bg "black" -fg "green").
We have two systems running 1.5 -- a i386 at 1.5 (1.5_ALPHA2 NetBSD
1.5_ALPHA2 (GENERIC) #2: Mon Aug 21 19:17:53 MEST 2000) -- apparently
loaded down binary -- and, a macppc at 1.5.1 (1.5.1_ALPHA
(EASTERN-1.5.1_ALPHA.backside) #0: Thu Jan 4 17:38:54 EST 2001). The
relevant xterms are dated:
i386 at 1.5_ALPHA2: Aug 21 10:39
macppc at 1.5.1_ALPHA: Dec 21 01:22
It looks like both were compiled under 1.5.
i386: Aug 13 21:05, maybe with 1.5, maybe not.
macppc: Sep 13 1999, well before 1.5.
I think both (i386 maybe compiled earlier) used to run fine in an
xterm window, although I'm not totally sure.
Some other program does this as well, I can't recall which.
Funny, though, when I read your messages, I took a flyer and tried:
lynx -book -nocolor
Apparently the problem's bound up in color emulations?
Julian, this may help:
This is a (nasty bad) base64 output from the i386 using
lynx -book >lynx.out:
This is a similar, but swell, base64 output from the v162 (netbsd
1.4.1) using lynx -book >lynx.out: