aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDave Love <[email protected]>2000-02-23 11:42:38 +0000
committerDave Love <[email protected]>2000-02-23 11:42:38 +0000
commite5a00c9c86915ff4707abee65328c459fcf0ecaa (patch)
tree2e815831fceff9a9ad5774078e53a4c1fc35bcfe
parent4ced66fd688c0e13c622e5943ca3ce361dff01ca (diff)
define-key-after change.
-rw-r--r--lispref/keymaps.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/lispref/keymaps.texi b/lispref/keymaps.texi
index 0826db07df..3dfc2576ca 100644
--- a/lispref/keymaps.texi
+++ b/lispref/keymaps.texi
@@ -2202,15 +2202,16 @@ put it in a particular place among the menu's existing items. If you
use @code{define-key} to add the item, it normally goes at the front of
the menu. To put it elsewhere in the menu, use @code{define-key-after}:
-@defun define-key-after map key binding after
+@defun define-key-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 be
of length one---a vector or string with just one element. But
@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}, then the new binding goes last, at the end of
-the keymap.
+@var{after} is @code{t} or omitted, then the new binding goes last, at
+the end of the keymap. New bindings are added before any inherited
+keymap.
Here is an example: