From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 55940@debbugs.gnu.org
Subject: bug#55940: macOS: <ns-show-prefs> displayed as keybinding for \\[customize]
Date: Mon, 13 Jun 2022 17:07:17 +0200 [thread overview]
Message-ID: <87mtegr49m.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkm=Vyjv4Neske8RRcA3EMbU-XknhRmmHmgwdhe4xCZQD9w@mail.gmail.com> (Stefan Kangas's message of "Mon, 13 Jun 2022 14:01:40 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> I have no idea how to press the key "<ns-show-prefs>" - I don't think
> there is such a button? There is also the keybinding "s-," which is
> slightly more useful (but not as useful as showing just "M-x
> customize", IMHO.)
That is pretty obscure. Do we have some mechanism for making
`substitute-command-keys' avoid such "keys"? I vaguely remember a
similar problem with a different event like this showing up in doc
strings...
On the other hand, as Po says -- "<ns-show-prefs>" is an actual key
binding in NS builds, apparently? So... Uhm...
> Please consider showing "s-," or "M-x customize" instead of
> "<ns-show-prefs>" here.
>
> Steps to reproduce:
> 0. emacs -Q
> 1. C-h v calendar-date-style RET
I see that the \\=`...' syntax doesn't allow saying \\=`M-x foo' (it has
to be a valid key stroke). I think it would make sense to allow
explicit M-x commands like this, so I've added this to Emacs 29.
But I've not amended the calendar-date-style doc string, because this
should be fixed in a more general way for `M-x customize', which I'm
sure is in a whole bunch of doc strings. I'm not sure what the solution
here would be, though. It would be easy enough to add a block-list
mechanism for `substitute-command-keys', but it seems a bit hacky.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-13 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:01 bug#55940: macOS: <ns-show-prefs> displayed as keybinding for \\[customize] Stefan Kangas
2022-06-13 12:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-13 15:07 ` Stefan Kangas
2022-06-14 6:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-14 9:02 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-14 9:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-14 10:58 ` Stefan Kangas
2022-06-14 11:20 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-13 15:07 ` Lars Ingebrigtsen [this message]
2022-06-13 15:16 ` Stefan Kangas
2022-06-13 15:20 ` Lars Ingebrigtsen
2022-06-14 12:05 ` Lars Ingebrigtsen
2022-06-17 22:40 ` Stefan Kangas
2022-06-18 12:06 ` Lars Ingebrigtsen
2022-06-21 12:39 ` Stefan Kangas
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=87mtegr49m.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55940@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).