From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: "52870@debbugs.gnu.org" <52870@debbugs.gnu.org>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#52870: [External] : bug#52870: Is displaying <menu-bar> bindings in describe-function useful?
Date: Sat, 15 Jan 2022 22:37:02 +0000 [thread overview]
Message-ID: <SJ0PR10MB54883ABCA18BB67FBBF1C729F3559@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87bl0dwbrd.fsf@gnus.org>
> 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>.
No, it's not. It doesn't tell you the key binding
(the menu it's in isn't the same thing). And it
tells you nothing about how to find out more about
that binding or to do something with its menu.
This ain't broke. Please don't fix it.
next prev parent reply other threads:[~2022-01-15 22:37 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
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 [this message]
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
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=SJ0PR10MB54883ABCA18BB67FBBF1C729F3559@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=52870@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).