From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@protonmail.com>, Po Lu <luangruo@yahoo.com>
Cc: gerd.moellmann@gmail.com, yikai@z1k.dev, eller.helmut@gmail.com,
74590@debbugs.gnu.org
Subject: bug#74590: 31.0.50 [scratch/igc branch]; key input sometimes skip fcitx input method preedit box
Date: Mon, 02 Dec 2024 18:51:26 +0200 [thread overview]
Message-ID: <86plma2fld.fsf@gnu.org> (raw)
In-Reply-To: <878qsykq4i.fsf@protonmail.com> (bug-gnu-emacs@gnu.org)
> Cc: Gerd Möllmann <gerd.moellmann@gmail.com>,
> Helmut Eller <eller.helmut@gmail.com>, 74590@debbugs.gnu.org
> Date: Mon, 02 Dec 2024 16:26:50 +0000
> From: Pip Cet via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> "Yikai Zhao" <yikai@z1k.dev> writes:
>
> > I have reproduced the issue with your patch, here's the relevant log:
>
> Thank you! So it seems we call XFilterEvent correctly but it incorrectly
> indicates that the keypress (event 2) should be handled by Emacs rather
> than the input method. That's rather puzzling, particularly since
> subsequent calls to XFilterEvent return 1, indicating that the key
> release is handled by the input method.
>
> I'm pretty much stumped at this point. It might be a timing difference
> between the MPS and non-MPS builds, but I think it's more likely to be
> a bug in our MPS code.
>
> > Please let me know if there's any other info I can provide.
>
> Well, you already tried setting x-gtk-use-native-input to t :-)
>
> One thing you could try is to run a full x11trace of the Emacs session
> and see whether anything unusual is in there. But that's not guaranteed
> to yield any results.
Maybe Po Lu (CC'ed) could have some additional ideas or comments.
prev parent reply other threads:[~2024-12-02 16:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 13:18 bug#74590: 31.0.50 [scratch/igc branch]; key input sometimes skip fcitx input method preedit box Yikai Zhao
2024-11-28 13:32 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-29 4:26 ` Yikai Zhao
2024-11-29 5:21 ` Gerd Möllmann
2024-11-29 5:55 ` Gerd Möllmann
2024-11-30 10:39 ` Helmut Eller
2024-11-30 10:55 ` Gerd Möllmann
2024-11-30 16:37 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 6:04 ` Gerd Möllmann
2024-12-01 7:33 ` Gerd Möllmann
2024-12-01 10:08 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 11:30 ` Gerd Möllmann
2024-12-02 8:58 ` Yikai Zhao
2024-12-02 10:06 ` Yikai Zhao
2024-12-02 8:56 ` Yikai Zhao
2024-12-02 16:26 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 16:51 ` 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=86plma2fld.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74590@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=gerd.moellmann@gmail.com \
--cc=luangruo@yahoo.com \
--cc=pipcet@protonmail.com \
--cc=yikai@z1k.dev \
/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).