From: Helmut Eller <eller.helmut@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Pip Cet <pipcet@protonmail.com>, Yikai Zhao <yikai@z1k.dev>,
74590@debbugs.gnu.org
Subject: bug#74590: 31.0.50 [scratch/igc branch]; key input sometimes skip fcitx input method preedit box
Date: Sat, 30 Nov 2024 11:39:07 +0100 [thread overview]
Message-ID: <87iks5xayc.fsf@gmail.com> (raw)
In-Reply-To: <m2wmgmbn39.fsf@gmail.com> ("Gerd Möllmann"'s message of "Fri, 29 Nov 2024 06:55:38 +0100")
On Fri, Nov 29 2024, Gerd Möllmann wrote:
>> Not sure if that is used in your build, but in x_display_info (xterm.h)
>> I see a number of struct frame pointers that are not fixed in fix_frame,
>> starting with
>>
>> struct frame *x_focus_frame;
>>
>> And if it's not that display info that is being used, I'd bet a small
>> amount that whatever is actually used (pgtk_display_info?) has a similar
>> problems.
>>
>> (Can't fix this myself, sorry, I only have macOS.)
I think the x_display_info struct (I guess usually only one exists) is
allocated in x_term_init (or pgtk_term_init) with igc_xzalloc_ambig. So
theoretically it doesn't need to be traced.
next prev parent reply other threads:[~2024-11-30 10:39 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 [this message]
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
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=87iks5xayc.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=74590@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.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).