From: Eli Zaretskii Date: Tue, 18 Jul 2023 13:17:15 +0000 (+0300) Subject: ; * doc/lispref/keymaps.texi (Modifying Menus): Add cross-references. X-Git-Tag: emacs-29.1-rc1~24 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=d172cd59854699c00de3b57a91e48ff70a4210f8;p=emacs.git ; * doc/lispref/keymaps.texi (Modifying Menus): Add cross-references. --- diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi index 66bb834192c..24b7738caff 100644 --- a/doc/lispref/keymaps.texi +++ b/doc/lispref/keymaps.texi @@ -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: