[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Improve input handling documentation
From: |
Stefan Monnier |
Subject: |
Re: Improve input handling documentation |
Date: |
Wed, 08 Sep 2010 11:11:07 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
> Meanwhile, here's what I have inferred, roughly, about input handling.
> Hopefully those familiar with emacs' guts can correct and improve it:
> <-------- keyboard input
> keyboard-coding-system
> <-------- unread-input-method-events
> [Input Method (optional, printable ascii chars only)]
> <-------- unread-post-input-method-events
> ???
> <-------- non-keyboard (e.g. mouse) events
> <-------- unread-command-events (and unread-command-char)
--------> read-char, read-event
> input-decode-map
> key-translation-map
> [local-]function-key-map
--------> read-key
> assorted keymaps (global, local, minor mode, emulation, char/text
> properties, overriding)
--------> read-key-sequence
> ???
> read-number, read-string, etc. (???)
That looks pretty good and would be a good addition.
One error: key-translation-map comes after [local-]function-key-map.
BTW: is there a good reason why C-x 8 is on key-translation-map rather
than in input-decode-map, function-key-map, or even global-map?
> NOTE: the description of read-key and input-decode-map makes it sound like
> read-event comes before coding systems, but empirically this is not true.
input-decode-map doesn't decode coding-systems but things like
escape sequences.
Stefan "who wants to obsolete key-translation-map"