unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.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: Tue, 08 Mar 2022 21:35:21 +0800	[thread overview]
Message-ID: <87a6e0k1nq.fsf@yahoo.com> (raw)
In-Reply-To: <8735jstw4s.fsf@gmx.net> (Stephen Berman's message of "Tue, 08 Mar 2022 14:24:35 +0100")

Stephen Berman <stephen.berman@gmx.net> writes:

> With that Super_L (the Windows key) is again recognized as `/' in
> emacs-29 and also in Firefox.

That confirms it's not really a bug in Emacs.  But I will look for a
better solution to this problem (the commit which introduced this
problem was originally put in to satisfy buggy input methods which act
on modifier keys, but don't filter them out).  Thanks.

> Why does this work but having the mappings in .Xmodmap doesn't?  (I
> also tried putting those three mappings after the five mappings I've
> been using for years in .Xmodmap, but it makes no difference.)

As for that, I have no idea.





  reply	other threads:[~2022-03-08 13:35 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 [this message]
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=87a6e0k1nq.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54289@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --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).