From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 55940@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#55940: macOS: <ns-show-prefs> displayed as keybinding for \\[customize]
Date: Tue, 14 Jun 2022 11:02:11 +0200 [thread overview]
Message-ID: <m1edzrpqi4.fsf@yahoo.es> (raw)
In-Reply-To: <87o7yvaicf.fsf@yahoo.com> (Po Lu's message of "Tue, 14 Jun 2022 14:07:28 +0800")
Po Lu <luangruo@yahoo.com> writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
>> Aha, thanks. I can't find it in '(emacs) Mac / GNUstep Events' but I
>> might be missing something. (Also: The other events there seem to be
>> missing index entries; maybe we would want to add such entries.)
>
> Done.
>
>> Adding this event to the manual is useful, but I still think that, for
>> the purposes of command substitution, it would be better to display an
>> actual keybinding rather than an event.
>
> I have no opinion towards that, since I don't actually use Mac OS.
I think it's fine to only update the documentation. We can expand the
text a bit and say that <ns-open-prefs> is usually sent by the OS when
Emacs is the front process and the user presses `Cmd-,' (comma). This
is officially documented, at least for macOS
(https://support.apple.com/en-us/HT201236). Similarly, we already say
that the fonts panel event is sent with `Cmd-t`.
If we had common events indexed in the manuals, users could ask Emacs
about any of them with C-h S, for example. Improving the
self-documenting features in Emacs is an alternative that I like more
compared to changing the displayed text depending on if there's only
events and no keybindings bound to a function, for example.
next prev parent reply other threads:[~2022-06-14 9:02 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 [this message]
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
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=m1edzrpqi4.fsf@yahoo.es \
--to=bug-gnu-emacs@gnu.org \
--cc=55940@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=mardani29@yahoo.es \
--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).