From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ryan Johnson <ryanjohn@ece.cmu.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Improve input handling documentation
Date: Wed, 08 Sep 2010 11:11:07 +0200 [thread overview]
Message-ID: <jwv39tkbo2z.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4C82987A.4060300@ece.cmu.edu> (Ryan Johnson's message of "Sat, 04 Sep 2010 21:05:30 +0200")
> 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"
prev parent reply other threads:[~2010-09-08 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100904160740.988082D5@osgood.ece.cmu.edu>
2010-09-04 19:05 ` Improve input handling documentation (was Re: Best way to intercept terminal escape sequences?) Ryan Johnson
2010-09-04 19:20 ` Improve input handling documentation Chong Yidong
2010-09-06 5:27 ` Ryan Johnson
2010-09-08 9:11 ` Stefan Monnier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv39tkbo2z.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ryanjohn@ece.cmu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.