From: Po Lu <luangruo@yahoo.com>
To: Madhu <enometh@meer.net>
Cc: emacs-devel@gnu.org
Subject: Re: problem with ibus + XIM with emacs XT ?
Date: Thu, 13 Jan 2022 21:29:36 +0800 [thread overview]
Message-ID: <87bl0fix1b.fsf@yahoo.com> (raw)
In-Reply-To: <20220113.185137.2182001463957804312.enometh@meer.net> (Madhu's message of "Thu, 13 Jan 2022 18:51:37 +0530 (IST)")
Madhu <enometh@meer.net> writes:
> That's a tough one - Switching the input method does not switch the
> input method - with xkb:il::heb if i type `a' i expect `ש' to be
> produced but I still get an `a'
Interesting. Is the correct input method applied when you restart
Emacs?
And if so, can you please set a breakpoint here, in this snippet of
xterm.c:
if (event->type == dpyinfo->xkb_event_type)
{
XkbEvent *xkbevent = (XkbEvent *) event;
if (xkbevent->any.xkb_type == XkbNewKeyboardNotify
|| xkbevent->any.xkb_type == XkbMapNotify)
{
if (dpyinfo->xkb_desc)
{
if (XkbGetUpdatedMap (dpyinfo->display,
(XkbKeySymsMask
| XkbKeyTypesMask
| XkbModifierMapMask
| XkbVirtualModsMask),
dpyinfo->xkb_desc) == Success)
{
---> XkbGetNames (dpyinfo->display,
XkbGroupNamesMask | XkbVirtualModNamesMask,
dpyinfo->xkb_desc);
}
else
{
XkbFreeKeyboard (dpyinfo->xkb_desc, XkbAllComponentsMask, True);
dpyinfo->xkb_desc = NULL;
}
x_find_modifier_meanings (dpyinfo);
}
}
}
And see if it is hit by you switching input methods? Thanks in advance.
> Yes. I tried --without-xinput2 build with configured features FREETYPE
> GMP JSON LIBXML2 NOTIFY INOTIFY PDUMPER SECCOMP X11 XFT XIM LUCID, and
> switching the input methods to xkb input methods work there.
>
> I can file a bug report if you let me know
Sure, make sure to add me to the X-Debbugs-Cc header. You can read more
about that here: https://debbugs.gnu.org/Reporting.html#xcc
next prev parent reply other threads:[~2022-01-13 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 4:09 problem with ibus + XIM with emacs XT ? Madhu
2022-01-13 4:55 ` Po Lu
2022-01-13 13:21 ` Madhu
2022-01-13 13:29 ` Po Lu [this message]
2022-01-14 0:53 ` Po Lu
2022-01-14 1:18 ` Madhu
2022-01-14 2:08 ` Po Lu
2022-01-14 5:00 ` Madhu
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=87bl0fix1b.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=enometh@meer.net \
/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).