From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
luangruo@yahoo.com,
Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: 67070@debbugs.gnu.org, me@eshelyaron.com
Subject: bug#67070: 29.1; broken keybindings with emacs 29
Date: Mon, 25 Dec 2023 06:55:58 -0800 [thread overview]
Message-ID: <CADwFkmmbbzpnnTcofwFD-2CqBjPbuBdvsgmUMVQay5c-wyWjVQ@mail.gmail.com> (raw)
In-Reply-To: <831qcedvgw.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Ping! Can we please make some further progress with this issue?
What's the current status here?
>> From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
>> Cc: Eshel Yaron <me@eshelyaron.com>, Eli Zaretskii <eliz@gnu.org>,
>> 67070@debbugs.gnu.org
>> Date: Thu, 16 Nov 2023 15:33:52 +0100
>>
>> Enrico Scholz <enrico.scholz@sigma-chemnitz.de> writes:
>>
>> >> What if you assign Super_L to a modifier bit just for testing?
>> >
>> > After an additional
>> >
>> > | add Mod3 = Super_L Super_R
>> >
>> > emacs reports 'H-M-x is undefined' on 'Meta_L (0x40) + x'.
>>
>> Doing
>>
>> | add Mod3 = Super_L Super_R Hyper_R Hyper_L
>>
>> generates the expected 'M-x'
>>
>>
>>
>> The Super or Hyper keys are probably coming from
>>
>> $ setxkbmap
>> $ xkbcomp :0 - | grep Mod4
>> modifier_map Mod4 { <LWIN> };
>> modifier_map Mod4 { <RWIN> };
>> modifier_map Mod4 { <SUPR> };
>> modifier_map Mod4 { <HYPR> };
>>
>> $ xmodmap ~/.Xmodmap
>> $ xkbcomp :0 - | grep Mod4
>> modifier_map Mod4 { <LALT> };
>> modifier_map Mod4 { <RALT> };
>> modifier_map Mod4 { <RWIN> };
>> modifier_map Mod4 { <META> };
>>
>> --> bad 'M-s-x' or 'H-M-x'
>>
>> $ xkbcomp :0 - | xkbcomp - :0
>> $ xkbcomp :0 - | grep Mod4
>> modifier_map Mod4 { <LALT> };
>> modifier_map Mod4 { <RALT> };
>> modifier_map Mod4 { <RWIN> };
>> modifier_map Mod4 { <META> };
>>
>> --> expected 'M-x'
>>
>>
>>
>> Enrico
>>
next prev parent reply other threads:[~2023-12-25 14:55 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 [this message]
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=CADwFkmmbbzpnnTcofwFD-2CqBjPbuBdvsgmUMVQay5c-wyWjVQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--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 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).