From: "Štěpán Němec" <stepnem@gmail.com>
To: Ryan Johnson <ryanjohn@ece.cmu.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, Kenichi Handa <handa@m17n.org>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
emacs-devel@gnu.org
Subject: Improve input handling documentation (was Re: Best way to intercept terminal escape sequences?)
Date: Sat, 04 Sep 2010 15:01:28 +0200 [thread overview]
Message-ID: <87bp8dfys7.fsf_-_@gmail.com> (raw)
In-Reply-To: <4C7F99A0.4090502@ece.cmu.edu> (Ryan Johnson's message of "Thu, 02 Sep 2010 14:33:36 +0200")
Ryan Johnson <ryanjohn@ece.cmu.edu> writes:
[...]
> It would be really nice to have, somewhere in the emacs docs, a diagram
> showing what processing happens to keyboard input, starting from raw bytes and
> UI events, and tracing them (or their translations) through coding systems,
> input methods, command loop, various keymaps, etc. and showing where in that
> process the different read-* functions intercept that data (and where the
> various unread-*-events reinsert things). A similar diagram for reading and
> writing files would probably also be useful.
Sounds great indeed!
[...]
> Unfortunately, even after spending so long on this problem I don't think I
> know enough to generate that diagram...
But perhaps you could come up with some initial version that others
could continue improving upon?
Štěpán
next prev parent reply other threads:[~2010-09-04 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100827142724.E1DD712F@hazard.ece.cmu.edu>
2010-08-27 14:44 ` Best way to intercept terminal escape sequences? Ryan Johnson
2010-08-27 15:40 ` Eli Zaretskii
2010-08-27 18:04 ` Ryan Johnson
2010-08-27 20:38 ` Eli Zaretskii
2010-08-27 23:54 ` Stefan Monnier
2010-08-28 7:54 ` Ryan Johnson
2010-08-28 14:47 ` Stefan Monnier
2010-08-28 20:34 ` Ryan Johnson
2010-08-31 23:12 ` Ryan Johnson
2010-09-02 10:53 ` Stefan Monnier
2010-09-02 12:33 ` Ryan Johnson
2010-09-04 13:01 ` Štěpán Němec [this message]
[not found] ` <jwvy6bfdp23.fsf-monnier+emacs@gnu.org>
2010-09-07 0:32 ` Kenichi Handa
2010-09-08 9:05 ` Stefan Monnier
[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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bp8dfys7.fsf_-_@gmail.com \
--to=stepnem@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=monnier@IRO.UMontreal.CA \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).