unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick OBrien via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 69246@debbugs.gnu.org
Subject: bug#69246: 30.0.50; persistent key input delay after using vc commands in pgtk
Date: Wed, 21 Feb 2024 16:09:09 +0000	[thread overview]
Message-ID: <yrYYbwRNF3kDwAI-7HSlGqIB8nyJpyUE6-tuuOSdijlyCkwz1_QkHHnttX1Bg-QlR9EVnjsGkwj1vrGpcwMnazotrsGGYZ9jSqj8tW8et8A=@proton.me> (raw)
In-Reply-To: <87zfvu6kyz.fsf@yahoo.com>

On Wednesday, February 21st, 2024 at 6:41 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> > 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?

I would think it's expected for the key to appear after pressing the key, not
releasing it.


On Wednesday, February 21st, 2024 at 6:49 AM, Po Lu <luangruo@yahoo.com> wrote:

> 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.

Running "GTK_IM_MODULE=none emacs -Q" and following the steps in the original
bug report, the lag appears to be fixed. I reproduced it three times, and each
time there was no lag. For reference, I tried again with GTK_IM_MODULE=fcitx
(how it was in the original bug report) and 4/4 times I experienced the lag.

I haven't ever experienced this sort of lag in Firefox or signal-desktop, two
gtk3 apps I regularly use. And just to clarify, the lag doesn't seem to lengthen
the interval between generated repeat key-presses. The repeated key-presses just
seem /choppier/, as if the frame-rate is lower. The lag is most obvious when
holding down a key and releasing after a single key appears.

I'll try using my normal config with GTK_IM_MODULE=none and see if I experience
the lag in everyday use.

Thanks






  reply	other threads:[~2024-02-21 16:09 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 [this message]
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='yrYYbwRNF3kDwAI-7HSlGqIB8nyJpyUE6-tuuOSdijlyCkwz1_QkHHnttX1Bg-QlR9EVnjsGkwj1vrGpcwMnazotrsGGYZ9jSqj8tW8et8A=@proton.me' \
    --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).