# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1042444744 0
# Node ID 943603fc2ef2c371e5c5dade0ab876fa775836e0
# Parent  94d20f0ab5166a7da30d5a9fecd84131d4315fa8
(Changing Key Bindings) <define-key>: Mention how to define a default binding.

diff -r 94d20f0ab516 -r 943603fc2ef2 lispref/keymaps.texi
--- a/lispref/keymaps.texi	Mon Jan 13 00:40:07 2003 +0000
+++ b/lispref/keymaps.texi	Mon Jan 13 07:59:04 2003 +0000
@@ -1063,6 +1063,10 @@
 meaningful.  (For a list of meaningful types, see @ref{Key Lookup}.)
 The value returned by @code{define-key} is @var{binding}.
 
+If @var{key} is @code{[t]}, this sets the default binding in
+@var{keymap}.  When an event has no binding of its own, the Emacs
+command loop uses the keymap's default binding, if there is one.
+
 @cindex invalid prefix key error
 @cindex key sequence error
 Every prefix of @var{key} must be a prefix key (i.e., bound to a keymap)
@@ -1072,8 +1076,8 @@
 
 If there was previously no binding for @var{key} in @var{keymap}, the
 new binding is added at the beginning of @var{keymap}.  The order of
-bindings in a keymap makes no difference in most cases, but it does
-matter for menu keymaps (@pxref{Menu Keymaps}).
+bindings in a keymap makes no difference for keyboard input, but it
+does matter for menu keymaps (@pxref{Menu Keymaps}).
 @end defun
 
   Here is an example that creates a sparse keymap and makes a number of