From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: 67070@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Eshel Yaron <me@eshelyaron.com>
Subject: bug#67070: 29.1; broken keybindings with emacs 29
Date: Thu, 16 Nov 2023 08:31:02 +0800 [thread overview]
Message-ID: <87sf56let5.fsf@yahoo.com> (raw)
In-Reply-To: <lyedgqoq8h.fsf@ensc-pc.intern.sigma-chemnitz.de> (Enrico Scholz's message of "Wed, 15 Nov 2023 18:55:58 +0100")
Enrico Scholz <enrico.scholz@sigma-chemnitz.de> writes:
> $ xmodmap -query
> xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
>
> shift Shift_L (0x32), Shift_R (0x3e)
> lock
> control Control_L (0x42), Control_R (0x69)
> mod1 Alt_L (0x85), Alt_R (0x87), Alt_L (0xcc)
> mod2 Num_Lock (0x4d)
> mod3 ISO_Level5_Shift (0xcb)
> mod4 Meta_L (0x40), Meta_R (0x6c), Meta_R (0x86), Meta_L (0xcd)
> mod5 ISO_Level3_Shift (0x5c)
What if you assign Super_L to a modifier bit just for testing?
I think this should coax XKB into assigning Super_L to a modifier
bit besides Mod4.
next prev parent reply other threads:[~2023-11-16 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 10:32 bug#67070: 29.1; broken keybindings with emacs 29 Enrico Scholz
2023-11-14 14:06 ` Eli Zaretskii
2023-11-14 15:10 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-15 17:55 ` Enrico Scholz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 0:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-16 14:26 ` Enrico Scholz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-16 14:33 ` Enrico Scholz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 9:37 ` Eli Zaretskii
2023-12-25 14:55 ` Stefan Kangas
2023-12-26 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-15 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87sf56let5.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=67070@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=luangruo@yahoo.com \
--cc=me@eshelyaron.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 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.