all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>,
	"52880@debbugs.gnu.org" <52880@debbugs.gnu.org>
Subject: bug#52880: [External] : bug#52880: "(elisp) Menu Keymaps") - recommend easy-menu over creating menu by hand
Date: Wed, 29 Dec 2021 21:57:51 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488FFCDCB517122AE7B1051F3449@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmnpD3HoLE+9Gh40qHJJEuUNAwGc-WuBeKdu9m-P0vbmMA@mail.gmail.com>

> The node (info "(elisp) Menu Keymaps") should recommend easy-menu over
> creating a menu by hand.  Instead of "Easy Menu" being the last thing in
> that node, it should be the first.

Why?

I disagree.

It should do as it does now, present defining
menus in general terms first: "How to make a
keymap that defines a menu".  It starts by
telling you that "A keymap acts as a menu if"
it has a prompt string. And in continues by
telling you the easiest way to construct a
keymap with a prompt string.  And so on.

Node Easy Menu tells you that you can _add_ a
menu to a keymap.  It doesn't tell you that a
keymap can _be_ a menu.  Which means that it
doesn't tell you what an Emacs menu is.
(And yet it's a subnode of node Menu Keymaps.)

Node Easy Menu doesn't lead to anything.  It
has no "next" node for a reason.  The other
nodes under Menu Keymaps build on each other.

      parent reply	other threads:[~2021-12-29 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 21:08 bug#52880: "(elisp) Menu Keymaps") - recommend easy-menu over creating menu by hand Stefan Kangas
2021-12-29 21:33 ` Lars Ingebrigtsen
2021-12-29 21:57   ` bug#52880: [External] : " Drew Adams
2021-12-29 22:43   ` Stefan Kangas
2021-12-30 14:43     ` Lars Ingebrigtsen
2021-12-29 21:57 ` Drew Adams [this message]

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=SJ0PR10MB5488FFCDCB517122AE7B1051F3449@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=52880@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 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.