From: Robert Pluim <rpluim@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: strange behaviour: Emacs ignoring one key on my keyboard,
Date: Thu, 14 Apr 2022 17:14:23 +0200 [thread overview]
Message-ID: <87lew74rzk.fsf@gmail.com> (raw)
In-Reply-To: <87fsmfivq6.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 14 Apr 2022 15:29:53 +0100")
>>>>> On Thu, 14 Apr 2022 15:29:53 +0100, Eric S Fraga <e.fraga@ucl.ac.uk> said:
Eric> So, somehow, maybe, Emacs is interpreting the *keycode* instead of the
Eric> *keysym*? Maybe something in the X11 parts of the Emacs code.
Eric> Somewhere to look, in any case, so I'm still investigating.
Eric> I have no need for a "super" key as I try to avoid all forms of key
Eric> chording as much as I can due to RSI issues.
Does 'xmodmap' show that you have a modifier mapped to that key? I
think emacs recently started trying to be smarter about that.
Robert
--
next prev parent reply other threads:[~2022-04-14 15:14 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
2022-04-14 15:14 ` Robert Pluim [this message]
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=87lew74rzk.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=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).