all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Helmut Eller <eller.helmut@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:55:42 +0100	[thread overview]
Message-ID: <m2mshhhtxt.fsf@gmail.com> (raw)
In-Reply-To: <87iks5xayc.fsf@gmail.com> (Helmut Eller's message of "Sat, 30 Nov 2024 11:39:07 +0100")

Helmut Eller <eller.helmut@gmail.com> writes:

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

Then we're good, sorry for the noise.

What made me suspicious is that we have this in fix_frame:

	Lisp_Object *nle = &FRAME_DISPLAY_INFO (f)->name_list_element;
	IGC_FIX12_OBJ (ss, nle);






  reply	other threads:[~2024-11-30 10:55 UTC|newest]

Thread overview: 18+ 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 [this message]
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
2024-12-04  4:55                   ` Yikai Zhao

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2mshhhtxt.fsf@gmail.com \
    --to=gerd.moellmann@gmail.com \
    --cc=74590@debbugs.gnu.org \
    --cc=eller.helmut@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.