Re: lynx-dev (key) Hex-ASCII values. . . ?

[pg]

In a recent note, Klaus Weide said:
> From pg Sun May 28 16:27 MDT 2000
> >Received: from cyclone.stortek.com (cyclone.stortek.com [129.80.22.130]) by 
> >swmail-atm6.StorTek.COM with ESMTP (8.7.6/8.7.3) id QAA26123 for 
> ><address@hidden>; Sun, 28 May 2000 16:27:57 -0600 (MDT)
> Received: from cyclone.stortek.com (cyclone.stortek.com [129.80.22.130]) by 
> swmail-atm6.StorTek.COM with ESMTP (8.7.6/8.7.3) id QAA26123 for 
> <address@hidden>; Sun, 28 May 2000 16:27:57 -0600 (MDT)
> Received: from cyclone.stortek.com (localhost [127.0.0.1])
>       by cyclone.stortek.com (8.9.3/8.9.3) with ESMTP id QAA21119
>       for <address@hidden>; Sun, 28 May 2000 16:27:29 -0600 (MDT)
> Received: from dfw-listserv1.email.verio.net 
> (dfw-listserv1-ext.email.verio.net [129.250.36.34])
>       by cyclone.stortek.com (8.9.3/8.9.3) with ESMTP id QAA21115
>       for <address@hidden>; Sun, 28 May 2000 16:27:28 -0600 (MDT)
> Received: from majordom by dfw-listserv1.email.verio.net with local (Exim 
> 3.12 #7)
>       id 12wBXD-0003Ni-00; Sun, 28 May 2000 22:27:51 +0000
> Date: Sun, 28 May 2000 17:27:50 -0500 (CDT)
> From: Klaus Weide <address@hidden>
> To: address@hidden
> Subject: Re: lynx-dev (key) Hex-ASCII values. . . ?
> In-Reply-To: <address@hidden>
> Message-ID: <address@hidden>
> MIME-Version: 1.0
> Sender: address@hidden
> Precedence: bulk
> Reply-To: address@hidden
> X-Mailing-List: lynx-dev
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Content-Length: 2243
> 
> On Sun, 28 May 2000, pAb-032871 wrote:
> 
> > Second, does anyone know the hex value of the Enter key on UNIX
> > and/or PC machines?  MacLynx doesn't respond to Enter on the keypad,
> > but *does* respond when you hit Return.  On a Mac, these keys
> > have two different ASCII/hex values; Enter=[03], Return=[0D].
> > 
> > Optional reading, from my notes:
> > 
> > <> [...] Adding hex-escaped
> > <> representations, and even pasting an Enter "character", with a hex
> > <> value of 03 into the KEYMAP section of lynx.cfg did nothing.  Messing
> 
> That would be a Control-C character.  I somehow doubt that that's
> correct.  Maybe at some lower keycode level, but not at the ASCII
> level at which lynx should see the characters.
> 
> > <> with a patch to make it re-type a "return" whenever the Enter key is
> > <> pressed, but that might happen too fast: MacLynx could be too busy
> > <> saying "press 'k' for list of commands" etc to notice the Return that
> > <> follows.
> 
> My (current) lynx doesn't say
>    press 'k' for list of commands
> when an unrecognized or invalid key is pressed, it says
>    press space for more, use arrow keys to move, '?' for help, 'q' to quit.
> But I assume you mean that (maybe the difference is a customization
> for Mac).
> 
> So lynx is seeing *some* character value, or it wouldn't produce that
> message.  (I'm assuming that the Mac port is not *completely*
> different from the common code wrt key handling.)  Or possibly a
> sequence of values.  Now you just have to find out which.  Trial and
> error...   (You might also try -trace - *sometimes* unrecognized
> escape sequences, at least, produce some trace output...)
> 
> > 
> > And that's pretty much what happened when I applied it -- nothing.
> > Change INFOSECS: to 0?  Anyone just starting on Lynx would NOT
> > benefit, even if it did work. . .
> > 
> > The escape sequence was
> > KEYMAP:0x03:ACTIVATE
> > but that could be wrong as well.
> 
> Have you tried
>   KEYMAP:0x0A:ACTIVATE
> 
> > Besides the "re-typing" option above, there's another one that
> > *might* be able to interrupt the keypress before MacLynx "gets"
> > it, replacing [03] it with the expected [0D]. . .
> 
> If it were seeing ^C, it should exit - unless that's changed
> for Mac, too.
> 
>    Klaus
> 
> 
> ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden
> 


-- 
StorageTek
INFORMATION made POWERFUL

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden