LYNX-DEV LYNX low level key mapping - Problems

[Michael Ritzert]

Eric Anderson writes:
 > I am looking for input from anyone else who may have had similar
 > difficulties with LYNX recognizing "special" keys of various terminals.
 > The problem I have is thus: On certain terminal types, special keys such
 > as PGUP, PGDN, END, etc, generate codes which lynx recognizes
 > incorrectly. For example pressing PGDN generates the sequence ^[[150q,
 > LYNX seems to ignore everything except the q, which causes it to quit. I
 > walked thru checking terminfo with one of our demi-gurus (I don't think
 > we have any deified gurus here). and he thinks that all of the keys are
 > getting handled correctly with the terminfo information. THe keys work
 > properly with our other software, other applications, emacs, etc. 
 > 
 > If anyone has seen, and even better, conquered, a problem like this,
 > please point me in the right direction (or just flat out tell me what I
 > gotta do :-) ) I will be happy to provide any more information that you
 > need.

The problem is not on this low level but one level higher: lynx uses a
table to make some of the special keys remappable. Its straightforward
generalisation would probably require a MASSIVE enlargement of this
table. I cannot judge if something like this is wanted by users as
well as by the main developers.
 > 

 > 
 > Thanks!

Michael Ritzert