From: Eli Zaretskii <eliz@gnu.org>
To: Nick OBrien <nick4f42@proton.me>
Cc: luangruo@yahoo.com, 69246@debbugs.gnu.org
Subject: bug#69246: 30.0.50; persistent key input delay after using vc commands in pgtk
Date: Sun, 25 Feb 2024 07:55:57 +0200 [thread overview]
Message-ID: <86h6hxxf2q.fsf@gnu.org> (raw)
In-Reply-To: <_BC5piJwFHcmUwixCvb9YFpPhY3PqVixGlnqY0I8emjen6P4KXK7g7Cosc0mgmhPOY3TbA8QPHZshPRGuvD-NaVYSr_1EG0PQ_fT8iy6NHE=@proton.me> (message from Nick OBrien on Sat, 24 Feb 2024 22:24:04 +0000)
> Date: Sat, 24 Feb 2024 22:24:04 +0000
> From: Nick OBrien <nick4f42@proton.me>
> Cc: 69246@debbugs.gnu.org
>
> A few updates:
>
> - After using my normal emacs config with GTK_IM_MODULE=none for a few
> days, I did not encounter the input lag. When previously using
> GTK_IM_MODULE=fcitx, I would have encountered the lag multiple times
> during the same pattern of use.
>
> - I tried installing ibus and following the steps in the original bug
> report with GTK_IM_MODULE=ibus. I encountered the same lag I did with
> fcitx.
Thanks for getting back to us. AFAIU, this is a more-or-less general
problem, which happens with many GTK input methods, perhaps all of
them. We now have an entry in PROBLEMS about this.
prev parent reply other threads:[~2024-02-25 5:55 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
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 [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
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=86h6hxxf2q.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).