# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1152119249 0
# Node ID ac52c6d8a154eb59ff38f5953229960478698e41
# Parent  e712aec3ce09fcbea915d5433a30f639a656b0ac
(Changing Key Bindings): Cleanup.
Add xref to Key Binding Conventions.

diff -r e712aec3ce09 -r ac52c6d8a154 lispref/keymaps.texi
--- a/lispref/keymaps.texi	Wed Jul 05 17:05:41 2006 +0000
+++ b/lispref/keymaps.texi	Wed Jul 05 17:07:29 2006 +0000
@@ -1198,6 +1198,10 @@
 Commands}).  You can also use @code{define-key}, a more general
 function; then you must specify explicitly the map to change.
 
+  When choosing the key sequences for Lisp programs to rebind, please
+follow the Emacs conventions for use of various keys (@pxref{Key
+Binding Conventions}).
+
 @cindex meta character key constants
 @cindex control character key constants
   In writing the key sequence to rebind, it is good to use the special
@@ -1219,11 +1223,11 @@
 @code{C-H-left}.  One advantage of such lists is that the precise
 numeric codes for the modifier bits don't appear in compiled files.
 
-  For the functions below, an error is signaled if @var{keymap} is not
-a keymap or if @var{key} is not a string or vector representing a key
-sequence.  You can use event types (symbols) as shorthand for events
-that are lists.  The @code{kbd} macro (@pxref{Key Sequences}) is a
-convenient way to specify the key sequence.
+  The functions below signal an error if @var{keymap} is not a keymap,
+or if @var{key} is not a string or vector representing a key sequence.
+You can use event types (symbols) as shorthand for events that are
+lists.  The @code{kbd} macro (@pxref{Key Sequences}) is a convenient
+way to specify the key sequence.
 
 @defun define-key keymap key binding
 This function sets the binding for @var{key} in @var{keymap}.  (If