From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>,
67070@debbugs.gnu.org, Enrico Scholz <enrico.scholz@ensc.de>
Subject: bug#67070: 29.1; broken keybindings with emacs 29
Date: Tue, 14 Nov 2023 16:10:24 +0100 [thread overview]
Message-ID: <m134x85q1r.fsf@dazzs-mbp.home> (raw)
In-Reply-To: <83zfzgsa3r.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Nov 2023 16:06:16 +0200")
>> 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'.
FWIW I had a similar issue a few weeks ago, with Emacs master. I don't
think it was an Emacs problem though, IIRC I ended up resolving it by
tweaking my ~/.Xmodmap, adding or reordering a `clear` line.
When you say that you press `M-x`, which key exactly are you pressing?
A good way to gain more insight here would be to start `xev` and note
which keycodes it records when you say `M-x`.
Best,
Eshel
next prev parent reply other threads:[~2023-11-14 15:10 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m134x85q1r.fsf@dazzs-mbp.home \
--to=bug-gnu-emacs@gnu.org \
--cc=67070@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=enrico.scholz@ensc.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.