From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 69246@debbugs.gnu.org, nick4f42@proton.me
Subject: bug#69246: 30.0.50; persistent key input delay after using vc commands in pgtk
Date: Thu, 22 Feb 2024 10:23:43 +0200 [thread overview]
Message-ID: <86y1bclxf4.fsf@gnu.org> (raw)
In-Reply-To: <87frxl6i5v.fsf@yahoo.com> (message from Po Lu on Thu, 22 Feb 2024 16:02:20 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: nick4f42@proton.me, 69246@debbugs.gnu.org
> Date: Thu, 22 Feb 2024 16:02:20 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What is the "unconventional manner" in which GTK Emacs responds to
> > keyboard input? And why do we do that?
>
> Emacs doesn't receive ASCII keyboard input as strings delivered by the
> input method, but as unprocessed key events with metadata such as active
> modifier masks, timestamps and keycodes, which is self-explanatory.
Thanks, but it seems like something was left out of this description:
you started by saying that Emacs _responds_ to keyboard input in some
unexpected way, but here you are talking about how Emacs _receives_
keyboard input, and say nothing about how we _respond_ to it. Why
would GTK care how Emacs _receives_ input if we don't tell it back
something about that input?
next prev parent reply other threads:[~2024-02-22 8:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 20:38 bug#69246: 30.0.50; persistent key input delay after using vc commands in pgtk Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 19:04 ` Eli Zaretskii
2024-02-18 19:21 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 19:31 ` Eli Zaretskii
2024-02-18 20:36 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-19 3:28 ` Eli Zaretskii
2024-02-21 2:19 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 12:41 ` Eli Zaretskii
2024-02-21 12:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 16:09 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 1:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 6:45 ` Eli Zaretskii
2024-02-22 8:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 8:23 ` Eli Zaretskii [this message]
2024-02-22 8:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-24 22:24 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 5:55 ` Eli Zaretskii
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=86y1bclxf4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69246@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=nick4f42@proton.me \
/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).