From: Drew Adams <drew.adams@oracle.com>
To: 53202@debbugs.gnu.org
Subject: bug#53202: 27.2; Shift + function key not recognized
Date: Wed, 12 Jan 2022 05:40:26 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488326765ECC611D3DEA476F3529@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
Feel free to rename this bug report as appropriate.
And I'm not sure if it should be a report about missing doc (or doc I
didn't fine) or a report about bugged behavior. I'm hoping that what I
don't understand is in fact documented, and I just didn't find that
doc.
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 looked in the Emacs and Elisp manuals, checking index entries that
have "shift" or "function key" in them, but I didn't notice anything
that explained why that key isn't recognized.
But if I do the same thing with (kbd "S-<f3>") there's no such problem.
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.
In GNU Emacs 27.2 (build 1, x86_64-w64-mingw32)
of 2021-03-26 built on CIRROCUMULUS
Repository revision: deef5efafb70f4b171265b896505b92b6eef24e6
Repository branch: HEAD
Windowing system distributor 'Microsoft Corp.', version 10.0.19042
System Description: Microsoft Windows 10 Pro (v10.0.2009.19042.1348)
next reply other threads:[~2022-01-12 5:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 5:40 Drew Adams [this message]
2022-01-12 7:15 ` bug#53202: 27.2; Shift + function key not recognized 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
2022-01-12 15:46 ` bug#53202: [External] : " 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=SJ0PR10MB5488326765ECC611D3DEA476F3529@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=53202@debbugs.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.
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.