aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStefan Monnier2001-10-12 01:33:41 +0000
committerStefan Monnier2001-10-12 01:33:41 +0000
commit33a425c45d095f6683f6f2b35eea5297d4add8e2 (patch)
tree9fd9e1f9ff2ad5fa432738b4432461dc1169844d
parent0b41c65c36066eda80149034baa47bf2e36b1dae (diff)
downloademacs-33a425c45d095f6683f6f2b35eea5297d4add8e2.tar.gz
emacs-33a425c45d095f6683f6f2b35eea5297d4add8e2.zip
Describe the meaning of a nil binding.
-rw-r--r--lispref/keymaps.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/lispref/keymaps.texi b/lispref/keymaps.texi
index 1877527dd90..8dfd2db8dfc 100644
--- a/lispref/keymaps.texi
+++ b/lispref/keymaps.texi
@@ -131,6 +131,11 @@ compact way to record lots of bindings. A keymap with such a vector is
131called a @dfn{full keymap}. Other keymaps are called @dfn{sparse 131called a @dfn{full keymap}. Other keymaps are called @dfn{sparse
132keymaps}. 132keymaps}.
133 133
134A @code{nil} binding is used to mean that a key is explicitly not bound.
135Just like any other binding, it takes precedence over a default binding
136or a binding in the parent keymap, but on the other hand, it does not
137take precedence over keymaps of lower priority.
138
134When a keymap contains a vector, it always defines a binding for each 139When a keymap contains a vector, it always defines a binding for each
135@sc{ascii} character, even if the vector contains @code{nil} for that 140@sc{ascii} character, even if the vector contains @code{nil} for that
136character. Such a binding of @code{nil} overrides any default key 141character. Such a binding of @code{nil} overrides any default key