unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Po Lu <luangruo@yahoo.com>
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 15:29:00 +0000	[thread overview]
Message-ID: <SJ0PR10MB548849EA0C37D1BB593CC606F3529@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87czkxs9vi.fsf@yahoo.com>

> Perhaps MS-Windows treats F10 as a menu bar accelerator 
> and eats that key, like the PGTK build does.

Shift + F10 is special for MS Windows, it seems,
so it's plausible that it can't be available to
Emacs.  Confirmation would be good.

Note that <f10> itself can be bound in Emacs.
Likewise <M-f10> and <C-f10>.  It seems to be only
<S-f10> that's unavailable.

If that's the case, maybe some mention in the doc
would be good.  E.g., if some Shift combinations,
in particular, are sometimes not available on some
platforms, maybe mention that fact.

Or if this isn't particularly true of Shift, then
maybe just some mention somewhere that some key
sequences might not be available for Emacs on some
platforms.

And maybe tell users how to tell if a key isn't
available (e.g. if `C-h k' doesn't recognize the
key at all, that might well mean that there's no
way for Emacs to use it).





  reply	other threads:[~2022-01-12 15:29 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   ` Drew Adams [this message]
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

  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=SJ0PR10MB548849EA0C37D1BB593CC606F3529@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=53202@debbugs.gnu.org \
    --cc=luangruo@yahoo.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 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).