From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 54289@debbugs.gnu.org
Subject: bug#54289: 29.0.50; Emacs ignores xmodmap Super_L assignment
Date: Mon, 07 Mar 2022 16:24:06 +0100 [thread overview]
Message-ID: <875yopbxbd.fsf@gnus.org> (raw)
In-Reply-To: <87pmmyt2oj.fsf@rub.de> (Stephen Berman's message of "Mon, 07 Mar 2022 12:36:12 +0100")
Stephen Berman <stephen.berman@gmx.net> writes:
> In my latest build from master (details below), the Super_L assignment
> is ignored and Emacs does not react at all to pressing the Super_L key
> (the Menu assignment is still recognized).
[...]
> In GNU Emacs 29.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.24.31, cairo version 1.17.4)
> of 2022-03-06 built on strobelfs2
> Repository revision: 98d2dc6522114e4044077801f11a3ed8de9c1147
> Repository branch: master
> Windowing system distributor 'The X.Org Foundation', version 11.0.12101003
> System Description: Linux From Scratch r11.0-165
I'm unable to reproduce this on Debian/bullseye. Our conf looks pretty
similar:
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.31, cairo version 1.16.0)
of 2022-03-06 built on xo
Repository revision: 98d2dc6522114e4044077801f11a3ed8de9c1147
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101003
System Description: Debian GNU/Linux bookworm/sid
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-07 15:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 11:36 bug#54289: 29.0.50; Emacs ignores xmodmap Super_L assignment Stephen Berman
2022-03-07 15:24 ` Lars Ingebrigtsen [this message]
2022-03-07 15:53 ` Stephen Berman
2022-03-07 15:59 ` Lars Ingebrigtsen
2022-03-07 16:14 ` Stephen Berman
2022-03-08 0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 8:52 ` Stephen Berman
2022-03-08 10:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 10:21 ` Stephen Berman
2022-03-08 10:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 10:52 ` Stephen Berman
2022-03-08 11:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 11:40 ` Stephen Berman
2022-03-08 11:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 12:03 ` Stephen Berman
2022-03-08 12:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 13:24 ` Stephen Berman
2022-03-08 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 13:55 ` Stephen Berman
2022-03-08 13:52 ` Andreas Schwab
2022-03-08 14:02 ` Stephen Berman
2022-03-08 14:21 ` Andreas Schwab
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=875yopbxbd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54289@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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).