From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52870@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#52870: Is displaying <menu-bar> bindings in describe-function useful?
Date: Sat, 15 Jan 2022 20:09:44 +0800 [thread overview]
Message-ID: <87k0f1b3p3.fsf@yahoo.com> (raw)
In-Reply-To: <87bl0dwbrd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 15 Jan 2022 11:09:58 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> What is your rationale for this? Is it easier to accept if it is before
>>> the "Probably introduced" line?
>>
>> The rationale is that hardly anyone ever looks at the "Probably
>> introduced" line. Before it is slightly better, but not good enough:
>> some doc strings are very long, so the menu-bar bindings will be
>> pushed too far.
>
> I think saying explictly
>
> It can be invoked from the menu: "Help Menu" -> "Describe..."
>
> is a lot clearer (and helpful) for users than the current
>
> It is bound to C-h f, <help> f, <menu-bar> <help-menu> <describe>
> <describe-function>.
>
> Perhaps keeping it grouped with the binding info would be good, though.
> So:
>
> It is bound to C-h f and <help> f
> It can also be invoked from the menu: "Help Menu" -> "Describe" ...
>
> or something like that?
FWIW I think it would be a good idea to do something like this:
It is bound to C-h f, <help> f, <menu-bar> <help-menu> <describe>
<describe-function> (which means it can be invoked from the menu:
"Help Menu" -> "Describe" ...).
Though I don't think I got the wording completely right there.
next prev parent reply other threads:[~2022-01-15 12:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 12:40 bug#52870: Is displaying <menu-bar> bindings in describe-function useful? Stefan Kangas
2021-12-29 13:08 ` Lars Ingebrigtsen
2021-12-29 13:28 ` Eli Zaretskii
2021-12-29 14:49 ` Stefan Kangas
2021-12-29 16:51 ` Eli Zaretskii
2021-12-29 20:19 ` Stefan Kangas
2021-12-29 21:01 ` bug#52870: [External] : " Drew Adams
2021-12-30 7:15 ` Eli Zaretskii
2021-12-30 15:43 ` bug#52870: [External] : " Drew Adams
2022-01-15 10:09 ` Lars Ingebrigtsen
2022-01-15 10:28 ` Eli Zaretskii
2022-01-20 11:02 ` Lars Ingebrigtsen
2022-01-15 10:29 ` Stefan Kangas
2022-01-15 12:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-15 22:50 ` bug#52870: [External] : " Drew Adams
2022-01-15 23:44 ` Stefan Kangas
2022-01-16 2:59 ` Drew Adams
2022-01-15 22:37 ` Drew Adams
2021-12-29 15:25 ` Drew Adams
2022-04-25 19:15 ` Lars Ingebrigtsen
2022-04-28 6:49 ` Juri Linkov
2022-04-28 10:17 ` 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=87k0f1b3p3.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=52870@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--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 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.