From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
Eli Zaretskii <eliz@gnu.org>,
me@eshelyaron.com, 67070@debbugs.gnu.org
Subject: bug#67070: 29.1; broken keybindings with emacs 29
Date: Tue, 26 Dec 2023 09:56:12 +0800 [thread overview]
Message-ID: <87bkadd8w3.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmbbzpnnTcofwFD-2CqBjPbuBdvsgmUMVQay5c-wyWjVQ@mail.gmail.com> (Stefan Kangas's message of "Mon, 25 Dec 2023 06:55:58 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> What's the current status here?
The difficulty in such bugs where a modifier configuration set with
xmodmap does not apply correctly to Emacs 29 arise from XKB's deficient
backwards compatibility with such configurations. My suggestion is to
exchange the xmodmap configuration for an XKB equivalent, where the
relations between key and virtual modifier and that between virtual
modifier and modifier bit are set down in an unambiguous manner. In
addition to that, there could also be an option to disable XKB.
next prev parent reply other threads:[~2023-12-26 1:56 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
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 [this message]
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=87bkadd8w3.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 \
--cc=stefankangas@gmail.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).