[Top][All Lists]

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

Re: [Lynx-dev] Changes in lynx display

From: Thomas Dickey
Subject: Re: [Lynx-dev] Changes in lynx display
Date: Thu, 31 Mar 2005 14:43:15 -0500 (EST)

On Wed, 30 Mar 2005, Doug Kaufman wrote:

I just compiled 2.8.6dev.11 with patch 11i for mingw (under cygwin).
This is the first lynx I have compiled since dev.5. I noticed some
changes in the display; I don't know if these are related to the other
reports or not. The mingw port is compiled with PDCurses 2.6. Both dev.5
and dev.11 use the same curses library.

In dev.11, the cursor is to the right of the link for a
non-text-input-field. This is with "show cursor" off. If "show cursor"
is on, the cursor is to the left of the link. In dev.5 the cursor stays
in the lower right hand corner of the screen, except when at a text
input field.

I hadn't noticed this. Actually what I see is incorrect but different: I'm seeing the cursor at the end of the message line at the bottom,
rather than at the lower-right corner.

In dev.11, on the options page, long lines are wrapped. In dev.5 they
were truncated. In dev.11, when one of the long wrapped fields is
changed via the drop-down box, the wrapped part on the next line is not
updated. For an example, see the line for "links and form fields are

Perhaps that's specific to PDCurses.  Running with ncurses in a 20x65
xterm, I don't see that.  (I do see the line above the message line
cleared while the menu is visible, but restored when the menu is popped
down - that's with expert mode).  PDCurses' X11 port behaves properly
too (but I'll make a note to test on win32).

When printing "lynx -version", I noted that it still prints a reference
to moxienet for lynx ssl support. We should probably remove that. The
code is in src/LYMain.c.

Lynx -version reports:
Lynx Version 2.8.6dev.11 (05 Jan 2005)
libwww-FM 2.14FM, SSL-MM 1.4.1, OpenSSL 0.9.7g-dev, pdcurses 2.601
Built on cygwin Mar 30 2005 19:01:37

The "-MM" - actually the "libwww-FM 2.14FM" is in the same category -
we could simply remove both strings.

Thomas E. Dickey

reply via email to

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