unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Po Lu <luangruo@yahoo.com>
Cc: 54289@debbugs.gnu.org
Subject: bug#54289: 29.0.50; Emacs ignores xmodmap Super_L assignment
Date: Tue, 08 Mar 2022 11:52:45 +0100	[thread overview]
Message-ID: <87fsnsu35u.fsf@gmx.net> (raw)
In-Reply-To: <878rtklov8.fsf@yahoo.com> (Po Lu's message of "Tue, 08 Mar 2022 18:28:43 +0800")

On Tue, 08 Mar 2022 18:28:43 +0800 Po Lu <luangruo@yahoo.com> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> shift       Shift_L (0x32),  Shift_R (0x3e)
>> lock
>> control     Control_L (0x25),  Control_L (0x42),  Control_R (0x69)
>> mod1        Alt_L (0x40),  Meta_L (0xcd)
>> mod2        Num_Lock (0x4d)
>> mod3
>> mod4        slash (0x85),  Super_R (0x86),  slash (0xce),  Hyper_L (0xcf)
>> mod5        ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)
>>
>>> I suspect that some modifier is mapped to Super_L, alongside slash.
>>
>> Is the above output consistent with the five mappings in my .Xmodmap
>> file?
>
> No: mod4 is both slash

You mean forward slash and backslash?  I.e. mod4 subsumes the Super_L
and Menu keysyms?

>>> That is incorrect, so Emacs and Firefox are within their rights to
>>> ignore such a mapping.
>>
>> If so, how do I get the mapping of Super_L to slash back (at least in
>> Emacs)?
>
> Try adding this to your ~/.Xmodmap and evaluating it as well:
>
>   remove mod4 = Super_R
>   remove mod4 = Hyper_L
>
> Also add this if you're sure you don't want the actual slash to be
> treated as mod4:
>
>   remove mod4 = slash
>
> And see if that resolves the problem.  Also, please tell if that makes
> Firefox recognize the mapping as well.

I tried with all three remove mappings and also with just the first two,
but in both cases nothing changed, i.e., typing Super_L (the Windows key
on my keyboard) still produced nothing in emacs-29 (non-pgtk build).
Same in Firefox.  FWIW evaluating `xmodmap .Xmodmap' gives this output
(both with the lines you suggested adding and without them):

xmodmap:  .Xmodmap:16:  bad keysym in remove modifier list 'Caps_Lock', no corresponding keycodes
xmodmap:  .Xmodmap:18:  bad keysym target keysym 'Caps_Lock', no corresponding keycodes
xmodmap:  .Xmodmap:49:  bad keysym target keysym 'Super_L', no corresponding keycodes
xmodmap:  .Xmodmap:52:  bad keysym target keysym 'Menu', no corresponding keycodes
xmodmap:  4 errors encountered, aborting.

Nevertheless, only the Super_L mapping fails in emacs-29 (and Firefox).

Steve Berman





  reply	other threads:[~2022-03-08 10:52 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 [this message]
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=87fsnsu35u.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=54289@debbugs.gnu.org \
    --cc=luangruo@yahoo.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).