From: Eli Zaretskii <eliz@gnu.org>
To: Enrico Scholz <enrico.scholz@ensc.de>, Po Lu <luangruo@yahoo.com>
Cc: 67070@debbugs.gnu.org
Subject: bug#67070: 29.1; broken keybindings with emacs 29
Date: Tue, 14 Nov 2023 16:06:16 +0200 [thread overview]
Message-ID: <83zfzgsa3r.fsf@gnu.org> (raw)
In-Reply-To: <87pm0gmvgl.fsf@sinclair.bigo.ensc.de> (message from Enrico Scholz on Sat, 11 Nov 2023 11:32:26 +0100)
> From: Enrico Scholz <enrico.scholz@ensc.de>
> Date: Sat, 11 Nov 2023 11:32:26 +0100
>
> Emacs 29 seems to inject always a 'super' key event after 'meta'.
> E.g. when I try to press 'M-x', emacs reports
>
> | M-s-x is undefined
>
> Ditto with any other key combination which involves 'meta'.
>
> Things work as expected with emacs 28.3 and before.
>
>
> My ~/.Xmodmap is
>
> ---
> keycode 12 = 3 numbersign section
> keycode 20 = minus underscore ssharp
> keycode 26 = e E EuroSign
> keycode 54 = c C cent
> keycode 34 = bracketleft braceleft udiaeresis
> keycode 47 = semicolon colon odiaeresis
> keycode 48 = apostrophe quotedbl adiaeresis
> keycode 28 = t T XF86Time
>
> keycode 66 = Control_L
>
> !keycode 37 = Mode_switch Caps_Lock
> keycode 37 = Mode_switch
> keycode 133 = Alt_L
> keycode 64 = Meta_L
>
> !keycode 108 = Mode_switch
> keycode 108 = Meta_R Meta_R
> keycode 134 = Meta_R
> keycode 135 = Alt_R
>
> clear Mod1
> clear Mod4
> clear Lock
> clear control
> add Lock = Caps_Lock
> add control = Control_L Control_R
> add Mod1 = Alt_L Alt_R
> add Mod4 = Meta_L Meta_R
>
> keycode 67 = F1 F1
> keycode 68 = F2 F2
> keycode 69 = F3 F3
> keycode 70 = F4 F4
> keycode 71 = F5 F5
> keycode 72 = F6 F6
> keycode 73 = F7 F7
> keycode 74 = F8 F8
> keycode 75 = F9 F9
> !keycode 76 = F10 F10
> keycode 95 = F11 F11
> keycode 96 = F12 F12
> ---
Thanks.
Po Lu, any comments or suggestions?
next prev parent reply other threads:[~2023-11-14 14:06 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 [this message]
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
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
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=83zfzgsa3r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67070@debbugs.gnu.org \
--cc=enrico.scholz@ensc.de \
--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).