From: Stefan Monnier Date: Fri, 10 Apr 2020 21:04:19 +0000 (-0400) Subject: * doc/lispref/keymaps.texi (Extended Menu Items): Tweak :key-sequence X-Git-Tag: emacs-27.0.91~29 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=6057d79a4eb4b95037068a1e9335a2418b2da5ec;p=emacs.git * doc/lispref/keymaps.texi (Extended Menu Items): Tweak :key-sequence Don't make it sound like `:key-sequence nil` is any different than the absence of `:key-sequence`. And the performance advantage of `:key-sequence` disappeared long ago. --- diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi index 259efea3248..f3c984848e7 100644 --- a/doc/lispref/keymaps.texi +++ b/doc/lispref/keymaps.texi @@ -2224,23 +2224,13 @@ set the variable so that the button you clicked on becomes selected. @item :key-sequence @var{key-sequence} This property specifies which key sequence is likely to be bound to the -same command invoked by this menu item. If you specify the right key -sequence, that makes preparing the menu for display run much faster. +same command invoked by this menu item. If you specify a correct key +sequence, that sequence will be preferred over others. -If you specify the wrong key sequence, it has no effect; before Emacs +If you specify in incorrect key sequence, it has no effect; before Emacs displays @var{key-sequence} in the menu, it verifies that @var{key-sequence} is really equivalent to this menu item. -@item :key-sequence nil -This property indicates that there is normally no key binding which is -equivalent to this menu item. Using this property saves time in -preparing the menu for display, because Emacs does not need to search -the keymaps for a keyboard equivalent for this menu item. - -However, if the user has rebound this item's definition to a key -sequence, Emacs ignores the @code{:keys} property and finds the keyboard -equivalent anyway. - @item :keys @var{string} This property specifies that @var{string} is the string to display as the keyboard equivalent for this menu item. You can use