comparison lispref/keymaps.texi @ 39794:30c76f38ad7b

Describe the meaning of a nil binding.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Fri, 12 Oct 2001 01:33:41 +0000
parents a585fe0f948f
children 6123edb0c45e
comparison
equal deleted inserted replaced
39793:1d5b7d31671f 39794:30c76f38ad7b
129 @var{n} is the binding for the character with code @var{n}. This is a 129 @var{n} is the binding for the character with code @var{n}. This is a
130 compact way to record lots of bindings. A keymap with such a vector is 130 compact way to record lots of bindings. A keymap with such a vector is
131 called a @dfn{full keymap}. Other keymaps are called @dfn{sparse 131 called a @dfn{full keymap}. Other keymaps are called @dfn{sparse
132 keymaps}. 132 keymaps}.
133 133
134 A @code{nil} binding is used to mean that a key is explicitly not bound.
135 Just like any other binding, it takes precedence over a default binding
136 or a binding in the parent keymap, but on the other hand, it does not
137 take precedence over keymaps of lower priority.
138
134 When a keymap contains a vector, it always defines a binding for each 139 When 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
136 character. Such a binding of @code{nil} overrides any default key 141 character. Such a binding of @code{nil} overrides any default key
137 binding in the keymap, for @sc{ascii} characters. However, default 142 binding in the keymap, for @sc{ascii} characters. However, default
138 bindings are still meaningful for events other than @sc{ascii} 143 bindings are still meaningful for events other than @sc{ascii}