[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev problems with persistant screen garbage
|
From: |
Paul |
|
Subject: |
Re: lynx-dev problems with persistant screen garbage |
|
Date: |
Thu, 22 Jul 1999 21:31:53 -0400 (EWT) |
On Thu, 22 Jul 1999, Klaus Weide wrote:
@>
@>On Thu, 22 Jul 1999, Paul wrote:
@>> 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.
@>> @>
@>>
@>> After linking with slang, the problem went away. Seems there may be a
weird
@>> problem with ncurses 4.2 / xterm (XFree86 3.3.+) / www.fatbrain.com :)
@>
@>You didn't answer my question about 'display character set' - did you
@>check? Having something wrong there could cause something like this,
@>if it means lynx would write chars in the range 128-159 to the screen
@>and your font doesn't have anything there. And slang might handle that
@>case differently.
@>I would also check for a corrupted font, try different fonts.
@>
@>There are a lot of · in that page, maybe that has something to do
@>with it. There are also lots of "&target" which might be interpreted
@>as character entities; although 2.8.2 should be immune against that.
@>
@>I would make a local copy of the page, and see whether it shows the
@>same problem. Then start messing around with it - first thing would
@>be to replace &target with &target etc.
@>
@> Klaus
@>
Im very sorry, but Im afraid I misrepresented the version of lynx that
I have the problem with. I have the _source_ for 2-8-2, and the version
given in the options section (Lynx Version 2.8rel.2) of the executable I
was using, mislead me into thinking it was 2-8-2.
It appears I just have 2-8, and perhaps unsuprisingly 2-8-2 does not have
any problems linked to either slang or ncurses. :(
Which is a shame, because I narrowed it down to this, which breaks my
xterm using 2-8 before realizing I was using an old version:
----------------
<html>
<head>
</head>
<body>
<table border="0" cellpadding="0" cellspacing="0"
width="100%">
<tr>
<td valign="bottom" align="left" width="196"><a
href="http://www1.fatbrain.com/goto.cl?vm=c&target=http://www.fatbrain.com/home.html";><img
src="/graphics/navbar/fblogo_184x61.gif" width=184 height=61 border="0"
alt="Welcome to Fatbrain.com"></a></td>
</tr>
</table>
</body>
</html>
----------------
Substituting '&target' for '&target' makes it work right. Simply
making that substitution on the first occurance of '&target' in the
source to the original web page stops the whole page from breaking my
xterm also.
My char set is 'ISO Latin 1', and choosing others didnt seem to make
a difference.
I apologize if my mistake wasted anyones time.
So, Ill just say thankyou for responding to me, and that I appreciate
very much the efforts of those who have worked on, or continue to improve
lynx, because it is one of my favorite and most used pieces of software.
Paul
address@hidden