unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: strange behaviour: Emacs ignoring one key on my keyboard,
Date: Thu, 14 Apr 2022 15:29:53 +0100	[thread overview]
Message-ID: <87fsmfivq6.fsf@ucl.ac.uk> (raw)
In-Reply-To: eg3mkexiK2M4rSHotAFmrpwOWFN1w7XB9ErOJD7ClvXZ1bV1AhWJIAPPy3vus87EqH2iyu3FfdXBgLUWSCPlnIf1Oo7-tGWgLupyXx9SHy4=@protonmail.com

On Thursday, 14 Apr 2022 at 14:17, emacsq via Users list for the GNU Emacs text editor wrote:
> Did you try bisecting the problem by going back to previous emacs git
> versions to identify when the problem occurs?

No, I did not as I have no idea when this started happening (it's a key
that I did not use for a long time).

I have, however, sort of figured out what is happening: the Windows key
acts as "super" in Emacs and it seems to do so no matter what I tell the
system via xmodmap.

So, if I type "C-h c WINDOWSKEY d", I do get "s-d undefined" so the key
is being interpreted, just not as what xev and other tools say it is
(i.e. as F20, as I defined it using xmodmap).

So, somehow, maybe, Emacs is interpreting the *keycode* instead of the
*keysym*?  Maybe something in the X11 parts of the Emacs code.
Somewhere to look, in any case, so I'm still investigating.

I have no need for a "super" key as I try to avoid all forms of key
chording as much as I can due to RSI issues.

Thank you,
eric
-- 
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.3




  reply	other threads:[~2022-04-14 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 14:17 strange behaviour: Emacs ignoring one key on my keyboard, emacsq via Users list for the GNU Emacs text editor
2022-04-14 14:29 ` Eric S Fraga [this message]
2022-04-14 15:14   ` Robert Pluim
2022-04-14 16:21     ` Eric S Fraga

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=87fsmfivq6.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=help-gnu-emacs@gnu.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.
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).