Re: lynx-dev problems with persistant screen garbage

[Paul]

On Wed, 21 Jul 1999, Klaus Weide wrote:

@>
@>On Tue, 20 Jul 1999, Paul wrote:
@>
@>> Dear Whomever;
@>> 
@>>     Running lynx 2.8.2 w/ ssleay patch. Linux 2.2.10 glibc.
@>> 
@>> #ldd `which lynx`
@>>         libncurses.so.4 => /usr/lib/libncurses.so.4 (0x40003000)
@>>         libc.so.6 => /usr/lib/libc.so.6 (0x40044000)
@>>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
@>> 
@>>     Go to 'http://www.fatbrain.com' and enter something in the search
@>> box, hit go, and immeadiately I see that the status line isnt being
@>> cleaned up. The page loads, go back or elsewhere, and for me, the
@>> stuff from the search result page persists as garbage. ^w or ^l refresh
@>> but the garbage persists.
@>
@>What exactly does the 'garbage' look like?
@>

        Clearing of the screen becomes broken, and text lingers from each prior 
web page as 'garbage'. Pages are displayed propperly, but simply over-write
prior pages rather than clearing the window first.

@>Do you have cookies enabled?  disabled? automatically accepted?
@>(The first thing *I* see when I access that site is a cookie prompt.)
@>
@>Does this happen with other sites?  other pages on the same site?
@>
@>How are you using lynx - console, xterm, remote login/dialin?
@>
@>What is $TERM set to?
@>
@>How is the 'display character set' set? ('O'ptions screen / lynx.cfg)
@>
@>What's the screen/window size?  If you can change it, does changing
@>it change the 'garbage' effect?  Are LINES on COLUMNS environment
@>variables set; and if so, are they set correctly?
@>
@>What is the ncurses version?
@>
@>   Klaus
@>

  Dear Klaus;

        I have done some more investigating.
        After some more play, I see it is my xterm that is getting into a bad 
state.
        This is the only site I have ever seen do this, and simply visiting
the site is enough to screw up my xterm. (just loading www.fatbrain.com)
  It stays broken even after I quit lynx and 'clear' doesnt clear the whole 
screen, but only parts of it.
  Doing a 'soft reset' from xterm's internal menu fixes it, but tset/reset 
doesnt.

        I built 2.8.1 on my netbsd machine and it does not exhibit this problem
but if I telnet to the linux box and run 2.8.1 there using the same xterm, I 
do have the problem.
Rxvt, xiterm, and the linux console do not have this problem either for me.     
(My environment variables all look good.)

        On the linux box, I have ncurses4.2. On the netbsd box, its whatever
comes with netbsd 1.4. (plain curses2.2 ?) So, I guess ncurses on the
linux box might be to blame? I tried to compile using slang while writing
this, but something went wrong. Ill also check to see if there is a newer
ncurses, fix my slang and try again.

        It is funny this website happens to be poison for my xterm, and only
running my 'linux' lynx. I have used this lynx executable for over a year,
daily, and had no problems until now:)

        It looks to me now like it is probably not lynx' fault, but any input is
welcome.


Paul
address@hidden