lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Background Color


From: pg
Subject: Re: lynx-dev Background Color
Date: Sat, 17 Feb 2001 17:44:32 -0700 (MST)

In a recent note, Thomas Dickey said:

> Date: Wed, 14 Feb 2001 18:56:36 -0500
>  
> > >   what's $TERM set to (or infocmp output)
> 
I'm trying a different terminal emulator:
:r ! echo $TERM
xterm-ncsa

(This is deceptive; it's not an X client, but a self-contained
terminal emulator and rlogin client in a Macintosh application.)
This shows no misbehavior of the background color; it's
gray no matter what shell escapes and edits I do.  And I'm using
a 14.4 Kbps modem, so I can watch the screen redraws:

lynx-2.8.4dev.18
    screen paints blank gray
    home page written on gray background
! # (shell escape)
    shell output displays on white background
        as image of lynx display and gray background scrolls line-by-line
        off top of screen
exit # return to lynx
    lynx page and gray background painted in single operation
e # edit source of page
    vi displays on white background
:q! # return to lynx
    screen paints blank gray
    home page written on gray background
Q # exit lynx
    shell output displays on white background
        as image of lynx display and gray background scrolls line-by-line
        off top of screen

It's interesting that after a shell escape the background and text are
painted in a single operation; on initial startup of lynx and after
vi escape, the background is painted first, then the tet is drawn.

> > Do you want my config.cache or lynx_cfg.h, possibly off the list?
> no - output from
>       infocmp
> and
>       appres XTerm
> 
attached for xterm-ncsa

And back to the xterm-color: with the slow modem I can observe the repaint
operations in detail.

lynx-2.8.4dev.18
    screen paints blank gray from top to bottom
    screen turns white instantly (not from top to bottom)
    screen paints blank gray from top to bottom
    home page written on gray background
! # (shell escape)
    shell output displays on white background, including contents of
        screen prior to invoking lynx; lynx screen has vanished.
exit # return to lynx
    screen paints gray from top to bottom
    screen turns white instantly (not from top to bottom)
    lynx page printed from top to bottom on white background
! # (shell escape)
    shell output displays on white background, including contents of
        screen prior to invoking lynx; lynx screen has vanished.
exit # return to lynx
    screen turns white instantly (not from top to bottom; didn't
        get painted gray this time.)
    lynx page printed from top to bottom on white background
e # edit source of page
    stale shell output appears briefly on white background
    vi displays on white background
:q! # return to lynx
    stale shell output appears briefly on white background
    home page written on white background
Q # exit lynx
    old shell output restored on white background

lynx-2.8.4dev.18
    screen paints blank gray from top to bottom
    screen turns white instantly (not from top to bottom)
    screen paints blank gray from top to bottom
    home page written on gray background
e # edit source of page
    stale shell output appears briefly on white background
    screen paints blank gray from top to bottom
    screen turns white instantly (not from top to bottom)
    vi displays on white background
:q! # return to lynx
    stale shell output appears briefly on white background
    lynx page printed from top to bottom on white background
^L # attempt to refresh screen
    screen turns white instantly (not from top to bottom)
    lynx page printed from top to bottom on white background
/xxx find string xxx
    text of link containing xxx turns gray
arrowkeys
    links passed over turn gray
^L # attempt to refresh screen
    screen turns gray  instantly (not from top to bottom)
    home page written on gray background

etc.  There's a whole lot of unnecessary (but perhaps unavoidable)
refreshing going on.  And a whole lot of sometimes annoying memory
of prior states.  And I've observed other state transitions too
complicated to describe here.

Thanks,
gil
-- 
StorageTek
INFORMATION made POWERFUL

Attachment: ncsa.ti
Description: c program text

Attachment: ncsa.ap
Description: ascii text


reply via email to

[Prev in Thread] Current Thread [Next in Thread]