Re: LYNX-DEV Curses lib

[Kristin McNally]

Actually, the problem is that the win32 version of Lynx is compiled with a
curses lib that directly accesses the CONSOLE_SCREEN_BUFFER_INFO structure.
The reason this lib accesses the buffer is so that it can get the LINES and
COLS environment variables.  Trying to set these variables before Lynx
launches (ie putenv("LINES=24);) is useless because the curses lib gets
these parameters from the dwSize member variable of the
CONSOLE_SCREEN_BUFFER_INFO structure.   Because this lib uses these calls,
it makes it extremely difficult to redirect Lynx's std i/o, even though Lynx
is using stdin and stdout for its i/o.

I would be interested in talking with anyone who is using the win32 version
of Lynx.

Kristin McNally
Applications Developer
MOON Communications
address@hidden (preferred)
address@hidden

-----Original Message-----
From: T.E.Dickey <address@hidden>
To: address@hidden <address@hidden>
Date: Thursday, April 02, 1998 9:51 PM
Subject: Re: LYNX-DEV Curses lib


>> >>>>> "KM" == Kristin McNally <address@hidden> writes:
>>
>> KM> What curses lib would I want to compile lynx with if I wanted a
curses
>> KM> lib that really supports serial terminals rather than emulates them?
>>
>> That depends on your platform.  On Unix, any curses (or curses-like)
>> library will support serial terminals.  On OS/2, you must use ncurses,
>> as EMX-bsd curses are inadequate and PDCurses and Slang use direct
>> screen writes.  On Win-ever, I don't know.  Quite probably you need to
>> use ncurses if there is one for that backwater.
>probably - perhaps KM was referring to implementation of delays & padding -
>needed for serial terminals).  The libraries that use direct screen writes
>aren't likely to have the code to support that.
>
>> | Jason F. McBrayer              address@hidden |
>
>--
>Thomas E. Dickey
>address@hidden
>http://www.clark.net/pub/dickey