[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#52880: [External] : bug#52880: "(elisp) Menu Keymaps") - recommend e
From: |
Drew Adams |
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 |
> 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.