Re: lynx-dev ENABLE_SCROLLBACK & PARTIAL_DISPLAY conflict

[Michael Warner]

On Sun, Dec 27, 1998, Klaus Weide <address@hidden> wrote:

> On Sun, 27 Dec 1998, Michael Warner wrote:

        [...]

> > I'm using the same terminal emulator (TeraTerm) and curses lib
> > (Slang) as I have been forever, so I guess it's some sort of
> > three-way conflict between the terminal, SCROLLBACK, and (maybe?)
> > partial-display.
> 
> Could you test what happens if you disable partial display, and/or
> change PARTIAL_THRES?

OK, with proxying turned off and the lynx cache set to the
minimum "2":

  SCROLLBACK off                                         -> no problem
  SCROLLBACK on & PARTIAL off                            -> no problem
  SCROLLBACK on & PARTIAL on  & THRESHOLD = {-1|1|10|40} -> problem

So it looks like the THRESHOLD value doesn't matter.

I originally thought that pages pulled from the caching proxy
rendered OK regardless of the SCROLLBACK and PARTIAL settings,
but I was in error.  Proxy use seems to have no effect.  Pages
from lynx's cache DO render without the problem, however.

Also, the first screenful of the page flashes briefly, then
gets wiped in favor of the "title, 1st link, status line"
minimalism.

This is dev10, configured with:

--enable-externs --enable-persistent-cookies 
--enable-nsl-fork --with-screen=slang --with-zlib
--enable-forms-options --enable-gzip-help --enable-cgi-links 
--enable-warnings --enable-exec-links
--enable-exec-scripts --enable-alt-bindings 
--enable-debug --enable-find-leaks
--enable-internal-links --enable-kbd-layout 
--disable-underlines --enable-warnings

Several of those (kbd-layout, f'rinstance) are just there in
case I get around to trying to figure out what they do.

I couldn't find anything that looked out of the ordinary in
the trace output.

Anything else that might help you?

-- 
Michael Warner 
<address@hidden>