Re: comments on compose keys

Guest section DW (dwguest@win.tue.nl)
Thu, 7 Oct 1999 22:27:42 +0200 (MET DST)


From humbubba@smarty.smart.net Thu Oct 7 22:15:43 1999

> From: Rick Hohensee <humbubba@smarty.smart.net>
>
> ... The reason is I suggest a different arrangement for the default
> compose keys. 256, one more than is available normally, allows a full
> hexadecimal entry method, a Compose key hexpad.
> It has long annoyed me that that directness is absent,
> when it was present on much older machines and "toy" machines like the
> c64. The c64 didn't have an actual hexpad, but there was some key
> combination for all 256 bytes, which does not appear to be the case with a
> stock Linux. A hexpad is utterly general, and regular. The various
> sophisticated interfaces Linux provides other than this are great, but are
> not so great as to validate losing the things they are built on.
>
> But wait, Linux *does* have a hexpad, and also a decimal pad.
> No kernel or other changes required.
>
> Press left Alt, type a number on the keypad, release left Alt, and voila:
> you produced a byte with the specified decimal value.
> Press right Alt, type a number on the keypad, release right Alt, and voila:
> you produced a byte with the specified hexadecimal value.
>
> If you try and fail, you must update your keymap.
> Perhaps "loadkeys linux-with-alt-and-altgr.inc" will do.
> (There are several conventions around about how to get
> the hexadecimal A-F. The nicest one assigns these to
> Keypad keys NumLock, /, *, -, +, Enter, so that you remain
> on the keypad. You can also choose to use the ordinary letters.)
>
> Andries

I don't think that's the same. I am in dvorak, and haven't checked with
defkeymap.map, but I'm talking about

Composekey 4 e

produces the byte value 0x4e.

Reread what I wrote above. You have that today.
No kernel changes required. Only, you press RightAlt instead of Compose.


This raises another question; I don't suggest anyone document all the
possible actions, but a synopsis of the major classes of actions, 0x000,
0x100, 0x200 etc. that corresponds to the first table in dumpkeys -l is
well worth doing methinxth.

There is some information in the kbd.FAQ.
Long ago I wrote an article for Linux Journal.
The text can be found at http://www.win.tue.nl/~aeb/linux/kbd/Linux_keyboard_driver
That has the information you ask for, I think.

Andries

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/