mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2025-02-07 20:54:32 +00:00
* 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.
This commit is contained in:
parent
17a1bb5a03
commit
6057d79a4e
@ -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
|
||||
|
Loading…
x
Reference in New Issue
Block a user