From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Alexander Prähauser" <alexander.praehauser@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>, 65068-done@debbugs.gnu.org
Subject: bug#65068: 29.1; xkb-interception interaction causes problems with key combinations
Date: Sat, 26 Aug 2023 18:01:59 +0800 [thread overview]
Message-ID: <87msye15rc.fsf@yahoo.com> (raw)
In-Reply-To: <87msye9gev.fsf@gmx.at> ("Alexander Prähauser"'s message of "Sat, 26 Aug 2023 13:39:47 +0200")
Alexander Prähauser <alexander.praehauser@gmx.at> writes:
> It works! Thanks so much! Finally I can transition to the new Emacs
> version! Say, can you write a high-level summary about what you did so
> I can send it to the Stumpwm-people?
The remedy is disabling non-standard behavior imposed by the XFree86 XKB
library, through changing the ControlFallback X library control:
#ifdef XkbLC_ControlFallback
XkbSetXlibControls (dpyinfo->display, XkbLC_ControlFallback, 0);
#endif /* XkbLC_ControlFallback */
Otherwise, XLookupString (and XmbLookupString) endeavor to locate an
ASCII character within a different group if ControlMask is set and the
standard means of keycode mapping produce a function key. In your case,
the keycode array for AC11 still assigned ASCII characters to groups 2
through 4; consequently, group 2 would be consulted in lieu of the key
event's effective group.
I'm closing this bug as fixed; Eli, do you object to installing a
three-line fix incorporating only the code quoted in this e-mail on
emacs-29?
next prev parent reply other threads:[~2023-08-26 10:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8dv2ib3.fsf@gmx.at>
2023-08-09 0:02 ` bug#65068: 29.1; xkb-interception interaction causes problems with key combinations Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 13:31 ` Alexander Prähauser
2023-08-16 1:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-16 7:50 ` Alexander Prähauser
2023-08-16 8:02 ` Alexander Prähauser
2023-08-16 12:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-16 14:04 ` Alexander Prähauser
2023-08-17 1:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 2:37 ` Alexander Prähauser
2023-08-17 2:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 3:28 ` Alexander Prähauser
2023-08-17 4:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 13:35 ` Alexander Prähauser
2023-08-23 11:02 ` Alexander Prähauser
2023-08-23 11:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-23 14:05 ` Alexander Prähauser
2023-08-24 0:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 11:06 ` Alexander Prähauser
2023-08-24 9:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 14:12 ` Alexander Prähauser
2023-08-24 12:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 15:34 ` Alexander Prähauser
2023-08-25 2:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-25 10:11 ` Alexander Prähauser
2023-08-25 8:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87o7iv34z0.FSF@yahoo.com>
2023-08-25 10:36 ` Alexander Prähauser
2023-08-26 1:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-26 11:39 ` Alexander Prähauser
2023-08-26 10:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-26 10:08 ` 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=87msye15rc.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65068-done@debbugs.gnu.org \
--cc=alexander.praehauser@gmx.at \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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).