# HG changeset patch # User Dave Love # Date 951306158 0 # Node ID 498b7f6777b5895f9c2ba7360212e7072ef8dff4 # Parent 5ef5616e830494d515394deb97e3c97d7c4b30e7 define-key-after change. diff -r 5ef5616e8304 -r 498b7f6777b5 lispref/keymaps.texi --- a/lispref/keymaps.texi Wed Feb 23 11:40:06 2000 +0000 +++ b/lispref/keymaps.texi Wed Feb 23 11:42:38 2000 +0000 @@ -2202,15 +2202,16 @@ 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: