From: Stephen Berman <stephen.berman@gmx.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Po Lu <luangruo@yahoo.com>, 54289@debbugs.gnu.org
Subject: bug#54289: 29.0.50; Emacs ignores xmodmap Super_L assignment
Date: Tue, 08 Mar 2022 15:02:45 +0100 [thread overview]
Message-ID: <87pmmwsfsq.fsf@gmx.net> (raw)
In-Reply-To: <87mti0pn5i.fsf@igel.home> (Andreas Schwab's message of "Tue, 08 Mar 2022 14:52:09 +0100")
On Tue, 08 Mar 2022 14:52:09 +0100 Andreas Schwab <schwab@linux-m68k.org> wrote:
> On Mär 08 2022, Stephen Berman wrote:
>
>> Why does this work but having the mappings in .Xmodmap doesn't?
>
> As you have written yourself the mappings were never applied:
>
>> xmodmap: 4 errors encountered, aborting.
That's what it looks like. But then why do the mappings of Caps_Lock
and Menu work (and Super_L did until the commit in question)? I've been
using that .Xmodmap for years and never had a problem with the mappings
in Emacs till that commit (but only with the Super_L in Firefox). If
the mappings haven't been applied, why do the keys work as if they did?
I haven't set these keys in any other way that I'm aware of.
Steve Berman
next prev parent reply other threads:[~2022-03-08 14:02 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
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 [this message]
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=87pmmwsfsq.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=54289@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=schwab@linux-m68k.org \
/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).