GNU bug report logs - #69246
30.0.50; persistent key input delay after using vc commands in pgtk

Previous Next

Full log

Message #47 received at 69246 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 69246 <at> debbugs.gnu.org, nick4f42 <at> proton.me
Subject: Re: bug#69246: 30.0.50; persistent key input delay after using vc
 commands in pgtk
Date: Thu, 22 Feb 2024 10:23:43 +0200

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: nick4f42 <at> proton.me,  69246 <at> debbugs.gnu.org
> Date: Thu, 22 Feb 2024 16:02:20 +0800
> 
> Eli Zaretskii <eliz <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.