From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "53202@debbugs.gnu.org" <53202@debbugs.gnu.org>
Subject: bug#53202: [External] : Re: bug#53202: 27.2; Shift + function key not recognized
Date: Wed, 12 Jan 2022 16:00:18 +0000 [thread overview]
Message-ID: <SJ0PR10MB548832AFB68A6E0DC5C0FDE2F3529@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR10MB5488326765ECC611D3DEA476F3529@SJ0PR10MB5488.namprd10.prod.outlook.com>
> I'm not aware of any such thing for my system, but
> that doesn't mean there's no such thing going on.
>
> I tried `w32-register-hot-key', but it had no effect
> for S-F10.
I was wrong. I have a program, Snag-It (which I've
never used), which was grabbing F10. I turned that
off, and the problem disappeared.
Feel free to close this bug. But maybe the Emacs
manual could mention somewhere that if `C-h k'
followed by pressing some key doesn't seem to do
anything - doesn't recognize that the key was
pressed, then perhaps some other app is grabbing
that key, so that Emacs can't use it.
The manual has node `Windows Keyboard', but that's
just for MS Windows (and it doesn't prevent some
other app from preventing Emacs from using a key).
Maybe some more general indication of this "problem"
would be helpful.
next prev parent reply other threads:[~2022-01-12 16:00 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
2022-01-12 15:46 ` bug#53202: [External] : " Drew Adams
2022-01-12 16:50 ` Eli Zaretskii
2022-01-12 16:00 ` Drew Adams [this message]
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
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=SJ0PR10MB548832AFB68A6E0DC5C0FDE2F3529@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=53202@debbugs.gnu.org \
--cc=eliz@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 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).