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 20:59:39 +0800	[thread overview]
Message-ID: <87h788k3b8.fsf@yahoo.com> (raw)
In-Reply-To: <877d94tzvj.fsf@gmx.net> (Stephen Berman's message of "Tue, 08 Mar 2022 13:03:44 +0100")

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

> xmodmap:  up to 4 keys per modifier, (keycodes in parentheses):
>
> 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 ran `xmodmap .Xmodmap' with those lines added and then ran just
> xmodmap, getting the above ouput.  This is identical to the output of
> xmodmap I sent previously, without the added lines from you.  Do the
> added lines need to be in a particular order with respect to the
> existing lines?  Currently my .Xmodmap has these uncommented lines, in
> the order listed:
>
> remove Lock      = Caps_Lock
> keysym Caps_Lock = Control_L
> add    Control   = Control_L
> remove mod4 = Super_R
> remove mod4 = Hyper_L
> remove mod4 = slash
> keysym Super_L = slash
> keysym Menu = backslash
>
> Steve Berman

What happens if you run this command after loading the .Xmodmap file?

  $ xmodmap -e 'remove mod4 = Super_R' -e 'remove mod4 = Hyper_L' -e \
  'remove mod4 = slash'

Thanks.





  reply	other threads:[~2022-03-08 12:59 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 [this message]
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=87h788k3b8.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).