[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Klaus Weide
Subject: Re: lynx-dev (key) Hex-ASCII values. . . ?
Date: Tue, 30 May 2000 10:20:58 -0500 (CDT)

On Tue, 30 May 2000, pAb-032871 wrote:

> > 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...)
> All it did was add "343" to the "press space for more" message.

I don't really understand why you could see that (didn't find the
line that produces this output), but I'm glad it worked for you. :)

> This wasn't much help at first. . .  Until it was translated;
> dec:343 = hex:0157.
> !!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!

That's the same number as ncurses' keypad() token for Enter; from

  #define KEY_ENTER       0527            /* Enter or send (unreliable) */

I don't know why that's seen in MacLynx, since I have no idea how it's
compiled, but it appears to use a curses library similar enough to
ncurses (and have keypad() enabled).

Newer versions of lynx - since 1998-11-23 (2.8.2dev.7), see CHANGES -
should already map this to '\n' (if compiled with a (n)curses.h that
has that definition).

You can use that code - obviously you want to, if you have no better
way - but don't be surprised if it stops working in a future version,
or in a lynx compiled differently.

> Still asks me if I *really* want to quit when I hit CTRL-C too.
> Weird, but I'm not complaining.

CTRL-C is obviously different from ENTER, despite the fact that some Mac
tools happen to show the same code...

I think your lynx sees CTRL-C as 0x03, so a KEYMAP:0x03 should affect
it.  (But on UNIX, lynx normally doesn't "see" CTRL-C as a character
at all - it sees an interrupt instead, so the KEYMAP:0x03 would have
no effect.  Unless CTRL-C does not generate an interrupt, which can
be achieved with the stty command.)


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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]