From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 53202@debbugs.gnu.org
Subject: bug#53202: 27.2; Shift + function key not recognized
Date: Wed, 12 Jan 2022 15:08:24 +0200 [thread overview]
Message-ID: <83tue95cfr.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488326765ECC611D3DEA476F3529@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Wed, 12 Jan 2022 05:40:26 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> Date: Wed, 12 Jan 2022 05:40:26 +0000
>
> emacs -Q
>
> (global-set-key (kbd "S-<f10>") 'forward-char)
>
> C-h w forward-char ; Says it's bound to <S-f10>
>
> But Emacs doesn't recognize that key at all. E.g. `C-h k' followed by
> Shift with function-key <f10>: the key isn't recognized.
I cannot reproduce this. I tried on 2 different Windows systems, both
with Emacs 27 and Emacs 28, and they both recognize S-F10 fine; with
the provided recipe, S-F10 moves point one character forward, as
expected.
I suspect that your system has some system-wide customizations that
steal this key. Maybe try to use w32-register-hot-key to work around
that.
> Is this a product bug? A doc bug? Neither? Is it perhaps
> platform-dependent? I see this behavior also in older Emacs releases,
> so it's not new.
If it's something specific to your Windows installation, it will most
probably happen with any Emacs version.
next prev parent reply other threads:[~2022-01-12 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 5:40 bug#53202: 27.2; Shift + function key not recognized Drew Adams
2022-01-12 7:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-12 15:29 ` bug#53202: [External] : " Drew Adams
2022-01-12 13:08 ` Eli Zaretskii [this message]
2022-01-12 15:46 ` Drew Adams
2022-01-12 16:50 ` Eli Zaretskii
2022-01-12 16:00 ` Drew Adams
2022-01-13 7:00 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tue95cfr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53202@debbugs.gnu.org \
--cc=drew.adams@oracle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.