changeset 68705:0a6051c71556

(Key Lookup): Clarify wrt commands vs other functions. (Changing Key Bindings): Clarify when remapping is better than substitute-key-definition.
author Richard M. Stallman <rms@gnu.org>
date Wed, 08 Feb 2006 00:26:37 +0000
parents 1fa04be25dbe
children 0d97a839b475
files lispref/keymaps.texi
diffstat 1 files changed, 7 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/lispref/keymaps.texi	Wed Feb 08 00:25:01 2006 +0000
+++ b/lispref/keymaps.texi	Wed Feb 08 00:26:37 2006 +0000
@@ -933,8 +933,10 @@
 @item
 @cindex @code{lambda} in keymap
 If the @sc{car} of @var{list} is @code{lambda}, then the list is a
-lambda expression.  This is presumed to be a command, and is treated as
-such (see above).
+lambda expression.  This is presumed to be a function, and is treated
+as such (see above).  In order to execute properly as a key binding,
+this function must be a command---it must have an @code{interactive}
+specification.  @xref{Defining Commands}.
 
 @item
 If the @sc{car} of @var{list} is a keymap and the @sc{cdr} is an event
@@ -1282,9 +1284,9 @@
 
   The function @code{substitute-key-definition} scans a keymap for
 keys that have a certain binding and rebinds them with a different
-binding.  Another feature you can use for similar effects, but which
-is often cleaner, is to add a binding that remaps a command
-(@pxref{Remapping Commands}).
+binding.  Another feature which is cleaner and can often produce the
+same results to remap one command into another (@pxref{Remapping
+Commands}).
 
 @defun substitute-key-definition olddef newdef keymap &optional oldmap
 @cindex replace bindings