unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>,
	"52870@debbugs.gnu.org" <52870@debbugs.gnu.org>
Subject: bug#52870: [External] : bug#52870: Is displaying <menu-bar> bindings in describe-function useful?
Date: Wed, 29 Dec 2021 15:25:45 +0000	[thread overview]
Message-ID: <SJ0PR10MB548869E7C3F2D49C7845606BF3449@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmmL1L6ZujDXM0XqYCtttLSqyc-A62+zfmT+PEenihKBcg@mail.gmail.com>

> 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...>.

I don't see that in Emacs 22 through the latest
release (Emacs 27.2).  It was likely introduced
in Emacs 21.

Perhaps someone has changed it for Emacs 28/29?
If so, why?

This is what I see:

 It is bound to M, <menu-bar> <operate> <chmod>.
                                        ^^^^^^^

Why change the name of the (pseudo-)function
key to be that of a menu item (including `...'
no less)?  Then, if that menu-item name changes
are you going to change the name of the key,
and thus break code that refers to the previous
name?  (Apparently such breakage is already in
progress for Emacs 28/29, by replacing <chmod>.)

> 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.

What is it that you're confused about?

Yes, it's useful.  It's important to show all of
the bindings.  Ignore it if it doesn't interest you.

> 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.

No, it's not enough.

This is about help (`C-h...').  It's about seeing
the bindings together with the doc for the command.

>    In this case, we could have an option to revert to the old behavior.

The proposed "new" behavior has no reason to be
adopted (apart from your being confused and
distracted by it).  What's the need/purpose?
Just to remove helpful information that you're
not interested in?

Why do you suppose that that info was added to
this help output - for no reason?  Or just to
confuse and distract?

> b) Show it separately from other key bindings at the end,

Why?  These bindings are bindings, like the others.
They're neither more nor less important.  Why split
the locations?

And why wouldn't we want to show (all) the key
bindings up front.  For a command, showing key
bindings is super-helpful, succinct info.

>   maybe something like this:
> 
>   Probably introduced at or before Emacs version 24.3.
>   It can be invoked from the menu: "Operate" -> "Change Mode..."

Absolutely not.  It's not about the menu-item text.
It's about the _key sequence_: what Emacs itself
calls that sequence - how Emacs itself talks about
such keys.

  parent reply	other threads:[~2021-12-29 15:25 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
2021-12-29 15:25 ` Drew Adams [this message]
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=SJ0PR10MB548869E7C3F2D49C7845606BF3449@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=52870@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).