Re: lynx-dev Lynx 2.8.3.dev4+Slang 1.3.8: arrow keys not working?

[Klaus Weide]

On Fri, 16 Jul 1999, Ismael Cordeiro wrote:
> On Fri, 16 Jul 1999, T.E.Dickey wrote:
> 
> > > Hi. I just compiled the latest Lynx devel but I can't get my arrow keys
> > > to work.
> [snip]
> > 
> > mine work (I build 3 copies for my home machine; 1's slang and the arrow
> > keys work in that).
> > 
> > dev.4 deprecates some hardcoded escape sequences in favor of what's
> > defined in the terminfo - perhaps your $TERM points to something that has
> > the cursor keys in application mode or vice versa (e.g., \EOA versus
> > \E[A).
> 
> I have the same problem on Solaris (terminfo) and FreeBSD (termcap) with
> slang 1.3.7. The cursor keys don't work, only the numeric keypad.

LYStrings.c:

        EXTERN_KEY( "\033[A",   "^(ku)", UPARROW,       KEY_UP ),
        EXTERN_KEY( "\033OA",   "^(ku)", UPARROW,       KEY_UP ),

We could at least have some minimal fallback by changing this to

        EXTERN_KEY( "\033[A",   "^(ku)", UPARROW,       KEY_UP ),
        EXTERN_KEY( "\033OA",   "\033OA", UPARROW,       KEY_UP ),

the duplication of "^(ku)" seems pointless.  This change wouldn't add
any lines.  Similar for the other lines in that 'table[]' where the
second field duplicates that of another line.

Well I don't know what's the more likely escape sequence (that 
contradicts the TERM capabilities) that people typically need,
maybe instead it should be

        EXTERN_KEY( "\033[A",   "\033[A", UPARROW,       KEY_UP ),
        EXTERN_KEY( "\033OA",   "^(ku)", UPARROW,       KEY_UP ),


   Klaus