summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2001-11-02 07:11:18 +0000
committerRichard M. Stallman <rms@gnu.org>2001-11-02 07:11:18 +0000
commit6a0f8bed68b3669fce098382e161ca43ebefe6c2 (patch)
tree6c6efe7d8e3dab1f49c6abdf74e06535b9c07d07
parent998d7b3bf6b1d4c318eddf9a07a2ad4dd3db3bb6 (diff)
downloademacs-6a0f8bed68b3669fce098382e161ca43ebefe6c2.tar.gz
emacs-6a0f8bed68b3669fce098382e161ca43ebefe6c2.tar.bz2
emacs-6a0f8bed68b3669fce098382e161ca43ebefe6c2.zip
Explain why a parent for a non-sparse keymap is not useful.
-rw-r--r--lispref/keymaps.texi8
1 files changed, 7 insertions, 1 deletions
diff --git a/lispref/keymaps.texi b/lispref/keymaps.texi
index 8dfd2db8dfc..c087b968793 100644
--- a/lispref/keymaps.texi
+++ b/lispref/keymaps.texi
@@ -333,7 +333,7 @@ new parent keymaps that reflect what @var{parent} specifies for those
prefix keys.
@end defun
-Here is an example showing how to make a keymap that inherits
+ Here is an example showing how to make a keymap that inherits
from @code{text-mode-map}:
@example
@@ -342,6 +342,12 @@ from @code{text-mode-map}:
map)
@end example
+ A non-sparse keymap can have a parent too, but this is not very
+useful. A non-sparse keymap always specifies something as the binding
+for every numeric character code without modifier bits, even if it is
+@code{nil}, so these character's bindings are never inherited from
+the parent keymap.
+
@node Prefix Keys
@section Prefix Keys
@cindex prefix key