procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; * doc/lispref/keymaps.texi (Modifying Menus): Add cross-references.

Browse source
This commit is contained in:
Eli Zaretskii 2023-07-18 16:17:15 +03:00
parent 927e8b470f
commit d172cd5985
1 changed files with 9 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/lispref/keymaps.texi
View file

@ -3172,14 +3172,15 @@ the menu. To put it elsewhere in the menu, use @code{keymap-set-after}:
@defun keymap-set-after map key binding &optional after
Define a binding in @var{map} for @var{key}, with value @var{binding},
just like @code{define-key}, but position the binding in @var{map} after
the binding for the event @var{after}. The argument @var{key} should
represent a single menu item or key, and @var{after} should be a
single event type---a symbol or a character, not a sequence. The new
binding goes after the binding for @var{after}. If @var{after} is
@code{t} or is omitted, then the new binding goes last, at the end of
the keymap. However, new bindings are added before any inherited
keymap.
just like @code{keymap-set} (@pxref{Changing Key Bindings}), but
position the binding in @var{map} after the binding for the event
@var{after}. The argument @var{key} should represent a single menu
item or key, and should satisfy @code{key-valid-p} (@pxref{Key
Sequences}). @var{after} should be a single event type---a symbol or
a character, not a sequence. The new binding goes after the binding
for @var{after}. If @var{after} is @code{t} or is omitted, then the
new binding goes last, at the end of the keymap. However, new
bindings are added before any inherited keymap.
Here is an example: