From: Yikai Zhao <yikai@z1k.dev>
To: Pip Cet <pipcet@protonmail.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Helmut Eller" <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, 2 Dec 2024 16:58:01 +0800 [thread overview]
Message-ID: <CANMyjpgzg8mg3iuHdcE=ogS3R=z0M-FEeUpif3TiwuirCt=5Jw@mail.gmail.com> (raw)
In-Reply-To: <87h67nn2bs.fsf@protonmail.com>
On Sun, Dec 1, 2024 at 6:08 PM Pip Cet <pipcet@protonmail.com> wrote:
>
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
> > It probably isn't relevant because of this
> >
> > #ifdef HAVE_MPS
> > void free_glib_user_data (gpointer data, GClosure *closure)
> > {
> > igc_xfree (data);
> > }
> > #else
> > void free_glib_user_data (gpointer data, GClosure *closure)
> > {
> > return;
> > }
> > #endif
> >
> > Don't know where the allocation takes place.
>
> It's this code in gtkutil.h:
>
> #ifdef HAVE_MPS
> INLINE gpointer
> glib_user_data (void *o)
> {
> gpointer p = igc_xzalloc_ambig (sizeof (o));
> memcpy (p, &o, sizeof (o));
> return p;
> }
>
> INLINE void *
> get_glib_user_data (gpointer p)
> {
> return *(void **)p;
> }
> #else
> INLINE gpointer
> glib_user_data (void *o)
> {
> return (gpointer)o;
> }
>
> INLINE void *
> get_glib_user_data (gpointer p)
> {
> return (void *)p;
> }
> #endif
>
> Does that look correct to you?
>
> My understanding is that the GTK input method code is only used if
> x_gtk_use_native_input is true (which we'll have to wait for the OP to
> confirm or deny),
`x-gtk-use-native-input` is nil here, if that's what you are asking.
> but xg_create_frame_widgets always calls
> gtk_im_multicontext_new, so the problem might be in the GTK code...
>
> Pip
>
next prev parent reply other threads:[~2024-12-02 8:58 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 [this message]
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='CANMyjpgzg8mg3iuHdcE=ogS3R=z0M-FEeUpif3TiwuirCt=5Jw@mail.gmail.com' \
--to=yikai@z1k.dev \
--cc=74590@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=gerd.moellmann@gmail.com \
--cc=pipcet@protonmail.com \
/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).