From: Stefan Kangas <stefan@marxist.se>
To: 52870@debbugs.gnu.org
Subject: bug#52870: Is displaying <menu-bar> bindings in describe-function useful?
Date: Wed, 29 Dec 2021 04:40:56 -0800 [thread overview]
Message-ID: <CADwFkmmL1L6ZujDXM0XqYCtttLSqyc-A62+zfmT+PEenihKBcg@mail.gmail.com> (raw)
Severity: wishlist
For example, in Dired, I type `C-h f dired-do-chmod RET' and read:
It is bound to M, <menu-bar> <operate> <Change Mode...>.
Is the "<menu-bar> ..." part there very useful? I personally find it
confusing and distracting. This is true even when I am specifically
developing menus; I'd rather look at the menu definition and the
resulting menu bar.
I would therefore like to suggest either:
a) Displaying nothing at all for such bindings. The menu entries will
be shown in the menu itself, and that is enough.
In this case, we could have an option to revert to the old behavior.
b) Show it separately from other key bindings at the end, maybe
something like this:
Probably introduced at or before Emacs version 24.3.
It can be invoked from the menu: "Operate" -> "Change Mode..."
next reply other threads:[~2021-12-29 12:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 12:40 Stefan Kangas [this message]
2021-12-29 13:08 ` bug#52870: Is displaying <menu-bar> bindings in describe-function useful? 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
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=CADwFkmmL1L6ZujDXM0XqYCtttLSqyc-A62+zfmT+PEenihKBcg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=52870@debbugs.gnu.org \
/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).