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

[T.E.Dickey]

> 
> On Sat, Jul 17, 1999, T.E.Dickey wrote: 
> > > If we're having this many problems, something should DEFINITELY be  
> > > included at release time, because I'd expect this to bite a number of  
> > > users, and I don't expect anyone wants to see "Why don't my arrow keys  
> > > work with 2.8.3?" every couple days.  
> >  
> > um - we already agreed afaik to restore the hardcoded values for slang 
> > users. 
> > (but since it's a minor issue for which someone sent a workable patch, we 
> > can 
> > move on). 
>  
> Ah, I hadn't realized a decision was reached. 
sure (someone reported the problem and my answer was twofold: 1 that it
shouldn't have been a problem - is minor because it only happens when the
$TERM doesn't match the terminfo and 2 that it'd get fixed in dev.5).

-- apparently many of the people using slang are relying on it to adjust
   the terminal description into something workable.
  
> I'm all for getting rid of the hardcoded values because they make for 
> maintenance problems.  If we could just document where to fix it for 
> some of the easier problems (ie, go grab a working vt100 terminfo 
> entry from ftp.foo.tld), or provide compile-time switch to  
> enable/disable it, that'd be great. 

well, this is what I'm going to use for the fix (doesn't increase the number
of hardcoded values in the source code; they're all swept up into a little
pile).

Index: src/LYStrings.c
--- lynx2.8.3dev.4+/src/LYStrings.c     Wed Jul 14 12:44:55 1999
+++ lynx2.8.3dev.4a/src/LYStrings.c     Sat Jul 17 14:39:41 1999
@@ -685,7 +685,7 @@
 # ifdef VMS
 #  define EXTERN_KEY(string,string1,lynx,curses) {string,lynx}
 # else
-#  define EXTERN_KEY(string,string1,lynx,curses) {string1,lynx}
+#  define EXTERN_KEY(string,string1,lynx,curses) {string,lynx},{string1,lynx}
 # endif
 # define INTERN_KEY(string,lynx,curses)          {string,lynx}
 #else


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey