From 1c115e404e38d04b179a00c2ed1bbd48ff070984 Mon Sep 17 00:00:00 2001 From: Lars Ingebrigtsen Date: Sun, 13 Dec 2020 13:49:25 +0100 Subject: [PATCH] Clarify Extended Menu Items a bit more * doc/lispref/keymaps.texi (Extended Menu Items): Expand a bit more on how submenus are formed (bug#26428). --- doc/lispref/keymaps.texi | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi index 130ff0d8671..6635f50960a 100644 --- a/doc/lispref/keymaps.texi +++ b/doc/lispref/keymaps.texi @@ -2167,9 +2167,10 @@ string. Thus, the string need not be a constant. The third element, @var{real-binding}, can be the command to execute (in which case you get a normal menu item). It can also be a keymap, -which will result in a submenu. Finally, it can be @code{nil}, in -which case you will get a non-selectable menu item. This is mostly -useful when creating separator lines and the like. +which will result in a submenu, and @var{item-name} is used as the +submenu name. Finally, it can be @code{nil}, in which case you will +get a non-selectable menu item. This is mostly useful when creating +separator lines and the like. The tail of the list, @var{item-property-list}, has the form of a property list which contains other information. -- 2.39.2