summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorStefan Monnier <monnier@iro.umontreal.ca>2001-10-12 01:33:41 +0000
committerStefan Monnier <monnier@iro.umontreal.ca>2001-10-12 01:33:41 +0000
commit33a425c45d095f6683f6f2b35eea5297d4add8e2 (patch)
tree9fd9e1f9ff2ad5fa432738b4432461dc1169844d /lispref
parent0b41c65c36066eda80149034baa47bf2e36b1dae (diff)
downloademacs-33a425c45d095f6683f6f2b35eea5297d4add8e2.tar.gz
Describe the meaning of a nil binding.
Diffstat (limited to 'lispref')
-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
called a @dfn{full keymap}. Other keymaps are called @dfn{sparse
keymaps}.
+A @code{nil} binding is used to mean that a key is explicitly not bound.
+Just like any other binding, it takes precedence over a default binding
+or a binding in the parent keymap, but on the other hand, it does not
+take precedence over keymaps of lower priority.
+
When a keymap contains a vector, it always defines a binding for each
@sc{ascii} character, even if the vector contains @code{nil} for that
character. Such a binding of @code{nil} overrides any default key