From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69246@debbugs.gnu.org, Nick OBrien <nick4f42@proton.me>
Subject: bug#69246: 30.0.50; persistent key input delay after using vc commands in pgtk
Date: Wed, 21 Feb 2024 20:49:24 +0800 [thread overview]
Message-ID: <87zfvu6kyz.fsf@yahoo.com> (raw)
In-Reply-To: <86ttm2m1ls.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Feb 2024 14:41:03 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 21 Feb 2024 02:19:11 +0000
>> From: Nick OBrien <nick4f42@proton.me>
>> Cc: 69246@debbugs.gnu.org
>>
>> In other words, if I press and release a key at the same time, the lag isn't
>> noticeable. I only see the lag when I press a key and don't release it. When a
>> key is held down and auto-repeating, I don't notice a drastic speed difference
>> with or without the lag. The appearing characters just look choppier when the
>> lag is occurring.
>>
>> I realize this is an awkward bug to explain and reproduce, thanks for bearing
>> with me. More suggestions on how to narrow down the cause would be appreciated.
>
> Isn't it expected that the key only appears when it's released? Po
> Lu, any comments to this strange issue?
Do other GTK 3 programs exhibit this lengthening of the intervals
between generated repeat keypresses? What if the environment variable
GTK_IM_MODULE is set to `none'?
TIA.
next prev parent reply other threads:[~2024-02-21 12:49 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 [this message]
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
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=87zfvu6kyz.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=69246@debbugs.gnu.org \
--cc=eliz@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).