From: Eli Zaretskii <eliz@gnu.org>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: emacs-devel@gnu.org
Subject: Re: Does a diagram of the key input subsystem exist?
Date: Wed, 01 Sep 2021 16:35:42 +0300 [thread overview]
Message-ID: <83eea8quz5.fsf@gnu.org> (raw)
In-Reply-To: <ba507601-ae06-b2a1-899f-4d7108d3d274@piermont.com> (perry@piermont.com)
> Date: Wed, 1 Sep 2021 08:44:07 -0400
> Cc: emacs-devel@gnu.org
> From: "Perry E. Metzger" <perry@piermont.com>
>
> On 8/31/21 22:30, Eli Zaretskii wrote:
> >> Is there anything like a document or diagram that lists the steps,
> >> translation tables, maps, etc. that every keystroke goes through in its
> >> journey? My guess is no, but I thought I would ask.
> > You mean, the description of what the read_char does?
> >
> read_char is only a portion of the overall processing path, but a
> description of read_char would definitely need to be part of such a thing.
So what else, in addition to read_char, are you interested in? maybe
if you'd ask more specific question, we could answer some of them.
To answer your question: the only documentation of this I know of is
in the Command Loop chapter of the ELisp manual. Some more is in
large comments in keyboard.c.
I think we do understand the overall picture, and could describe it
(which it would perhaps then make sense to put the description into
the comments in keyboard.c), but only on a high enough level,
disregarding low-level details. You'd need to read the code to find
out the rest.
prev parent reply other threads:[~2021-09-01 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 20:54 Does a diagram of the key input subsystem exist? Perry E. Metzger
2021-09-01 2:30 ` Eli Zaretskii
2021-09-01 12:44 ` Perry E. Metzger
2021-09-01 13:35 ` Eli Zaretskii [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=83eea8quz5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.com \
/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.