aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChong Yidong <[email protected]>2006-09-11 02:39:16 +0000
committerChong Yidong <[email protected]>2006-09-11 02:39:16 +0000
commit3250aca208b13f138747c48b7549b41dfe91f4f6 (patch)
tree60921ac9c0974bbdb3bcd451a62ec0b0c5f7ebf8
parent42e76a876ddee4b46cbd96729da25d5dd12f0b8b (diff)
* keymaps.texi (Active Keymaps): Mention that key-binding checks
local maps.
-rw-r--r--lispref/ChangeLog5
-rw-r--r--lispref/keymaps.texi4
2 files changed, 9 insertions, 0 deletions
diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index f8713eb039..3ce4978d95 100644
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2006-09-10 Chong Yidong <[email protected]>
+
+ * keymaps.texi (Active Keymaps): Mention that key-binding checks
+ local maps.
+
2006-09-10 Kim F. Storm <[email protected]>
* display.texi (Forcing Redisplay): Document return value of
diff --git a/lispref/keymaps.texi b/lispref/keymaps.texi
index 13f4550a08..d876761a76 100644
--- a/lispref/keymaps.texi
+++ b/lispref/keymaps.texi
@@ -664,6 +664,10 @@ undefined in the keymaps.
The argument @var{accept-defaults} controls checking for default
bindings, as in @code{lookup-key} (above).
+When @var{key} is a vector containing an input event, such as a mouse
+click, @code{key-binding} first looks for the binding in the local
+keymap at the position specified by that event, if any.
+
When commands are remapped (@pxref{Remapping Commands}),
@code{key-binding} normally processes command remappings so as to
returns the remapped command that will actually be executed. However,