LYNX-DEV Wyse 150 keypad behavior

[Greg Barniskis]

At SCLS, we have Lynx 2.7.1 with fotemods patches (last updated circa 
July 1997). We seemed to have the "best" results (under HP-UX 10.x, with 
HP's optional ANSI C compiler installed) using these Makefile settings:

snake3:
        cd WWW/Library/snake; $(MAKE) CC="cc" LYFLAGS="-Ae -DUNIX \
                $(SITE_LYDEFS)"
        cd src; $(MAKE) all CC="cc" MCFLAGS="-O -Ae -DFANCY_CURSES -DUNIX 
\
                -DSNAKE -DUNDERLINE_LINKS -I../$(WWWINC) $(SITE_DEFS)" \
                LIBS="-lcurses -ltermcap \
                $(WAISLIB) $(SOCKSLIB) $(SITE_LIBS)" \
                WWWLIB="../WWW/Library/snake/libwww.a"

We have Wyse 150 terminals in VT100 mode connected to our intergrated 
library services host (an Ameritech Library Services' Dynix system). 
There are a number of terminal parameter settings required for use with 
this system. Terminals logged into Dynix may telnet to another host here 
to run a captive Lynx session.

When we start Lynx, the terminal's settings change from "Keypad = 
Numeric" and "Cursor Keys = Normal" to "Keypad = Application" and "Cursor 
Keys = Application". Is this a necessary evil of using Lynx, or just a 
side effect of our compilation options?

What I'm looking for is a way to stop those changes (if they are not 
necessary for Lynx's operation) or a way to force the terminal to switch 
back to our Dynix required settings when we quit from Lynx.

Any suggestions would be appreciated. TIA,

-----------------------------------------------------
Greg Barniskis                   address@hidden
Network Administrator                  (608) 266-6394
Library Interchange NetworK (LINK)      fax: 266-6068
South Central Library System (SCLS)       Madison, WI