# HG changeset patch
# User Chong Yidong <cyd@stupidchicken.com>
# Date 1148741771 0
# Node ID 1755e59e9a8adaffd2ed54c54ede8c1561a8e528
# Parent  aca1b9717822fb0c42552d9ce451222d9178d7e7
	* keymaps.texi (Key Sequences): Link to input events definition.
	(Format of Keymaps): Delete material duplicated in Keymap Basics.

diff -r aca1b9717822 -r 1755e59e9a8a lispref/ChangeLog
--- a/lispref/ChangeLog	Sat May 27 14:36:59 2006 +0000
+++ b/lispref/ChangeLog	Sat May 27 14:56:11 2006 +0000
@@ -1,5 +1,8 @@
 2006-05-27  Chong Yidong  <cyd@stupidchicken.com>
 
+	* keymaps.texi (Key Sequences): Link to input events definition.
+	(Format of Keymaps): Delete material duplicated in Keymap Basics.
+
 	* files.texi (Changing Files): Document updated argument list for
 	copy-file.
 
diff -r aca1b9717822 -r 1755e59e9a8a lispref/keymaps.texi
--- a/lispref/keymaps.texi	Sat May 27 14:36:59 2006 +0000
+++ b/lispref/keymaps.texi	Sat May 27 14:56:11 2006 +0000
@@ -45,10 +45,11 @@
 @cindex key sequence
 
   A @dfn{key sequence}, or @dfn{key} for short, is a sequence of one
-or more input events that form a unit.  The Emacs Lisp representation
-for a key sequence is a string or vector.  Unless otherwise stated,
-any Emacs Lisp function that accepts a key sequence as an argument can
-handle both representations.
+or more input events that form a unit.  Input events include
+characters, function keys, and mouse actions (@pxref{Input Events}).
+The Emacs Lisp representation for a key sequence is a string or
+vector.  Unless otherwise stated, any Emacs Lisp function that accepts
+a key sequence as an argument can handle both representations.
 
   In the string representation, alphanumeric characters ordinarily
 stand for themselves; for example, @code{"a"} represents @kbd{a} and
@@ -153,22 +154,6 @@
 @cindex full keymap
 @cindex sparse keymap
 
-  A @dfn{keymap} is a table mapping event types to definitions (which
-can be any Lisp objects, though only certain types are meaningful for
-execution by the command loop).  Given an event (or an event type) and a
-keymap, Emacs can get the event's definition.  Events include
-characters, function keys, and mouse actions (@pxref{Input Events}).
-
-  At any time, several primary keymaps are @dfn{active}---that is, in
-use for finding key bindings.  These are the @dfn{global map}, which is
-shared by all buffers; the @dfn{local keymap}, which is usually
-associated with a specific major mode; and zero or more @dfn{minor mode
-keymaps}, which belong to currently enabled minor modes.  (Not all minor
-modes have keymaps.)  The local keymap bindings shadow (i.e., take
-precedence over) the corresponding global bindings.  The minor mode
-keymaps shadow both local and global keymaps.  @xref{Active Keymaps},
-for details.
-
   Each keymap is a list whose @sc{car} is the symbol @code{keymap}.  The
 remaining elements of the list define the key bindings of the keymap.
 A symbol whose function definition is a keymap is also a keymap.  Use