Re: Howto Distinguish Prior from KP_Prior

Thomas Dickey staggered into the Black Sun and said:
Dances With Crows <danSPANceswithTRAPcrows@xxxxxxxxx> wrote:
Thomas Dickey staggered into the Black Sun and said:
actually xterm doesn't treat them identically, though in the default
configuration they are
That explains it; I just started an ordinary xterm and read stdin and
dumped the read chars in hex. Didn't mess with remapping things,
though now I see how to do that (grep xterm man page for "keymap").
keymaps may not work (the X library support for that was broken some
time ago. I was referring to things like this:

-kt keyboardtype
This option sets the keyboardType resource. Possible
values include: ``unknown'', ``default'',
``hp'', ``sco'', ``sun'' and ``vt220''.

Yikes. That's not quite as nifty as the keymap feature, though if it
works and the keymap feature doesn't, it could be useful. I did find
out that rxvt appears to support mapping keysyms to arbitrary strings a
few days ago, with strings like:

Rxvt.keysym.0xffb9: zorch

....in your ~/.Xdefaults file or whatever X resource file you're using.
So you push the key that generates keysym 0xffb9 (KP_9), rxvt inserts
the string "zorch". You can of course use escape sequences like \e and
\n to insert nonprinting chars. This might actually be another solution
for the OP's problem if he could deal with using rxvt instead of
whatever term emulator he was using. Although I don't know if the OP's
still reading this thread....

--
One OS to rule them all, with DRM to find them
One OS to bring them all and with the EULA bind them
In the Land of Redmond where the shadows lie.
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
.