Re: lynx-dev new command format (was transport)

[Larry W. Virden]

From: Philip Webb <address@hidden>

> you mentioned `lynxactioncode' (SIC) in your original discussion re `t',
> but a quick look at Users Guide &  lynx.cfg  finds no mention:

> lynx.cfg  speaks of `functions' & refers the user to  LYKeymap.c ,
> which has a table of values in the form  LYK_SOME_FUNCTION ,
> in both cases giving  > 1  mapping of some functions.

I just did a quick grep though the source code looking for the string
"lynxactioncode", ignoring case.  I found the string (without white
spaces) in:

./CHANGES
./samples/lynx-keymaps
./src/LYStrings.h
./src/LYKeymap.h
./src/LYKeymap.c
./src/LYStrings.c
./src/LYForms.c

I suspect that what we need to do is update the user's guide, man page,
lynx.cfg and anything else that references this concept to be consistent.

The authority table of available values appears to be in src/LYKeymap.c , where
I read:


/* * *  Tables mapping LynxKeyCodes to LynxActionCodes  * * */

/*
 *  Lynxkeycodes include all single-byte keys as well as codes
 *  for function keys and some special purposes.  See LYStrings.h.
 *  Extended lynxkeycode values can also contain flags for modifiers
 *  and other purposes, but here only the base values are mapped to
 *  lynxactioncodes.  They are called `keystrokes' in lynx.cfg.
 *
 *  Lynxactioncodes (confusingly, constants are named LYK_foo and
 *  typed as LYKeymapCode) specify key `functions', see LYKeymap.h.
 */


There are several tables containing mappings in that source file.  One
must be careful in changing the tables here since there is apparently
a dependency between at least one of these tables (revmap) and an enum
declaration in the keymap header file.

-- 
Larry W. Virden                 <URL: mailto:address@hidden>
<URL: http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-