aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2001-11-02 07:11:18 +0000
committerRichard M. Stallman2001-11-02 07:11:18 +0000
commit6a0f8bed68b3669fce098382e161ca43ebefe6c2 (patch)
tree6c6efe7d8e3dab1f49c6abdf74e06535b9c07d07
parent998d7b3bf6b1d4c318eddf9a07a2ad4dd3db3bb6 (diff)
downloademacs-6a0f8bed68b3669fce098382e161ca43ebefe6c2.tar.gz
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
333prefix keys. 333prefix keys.
334@end defun 334@end defun
335 335
336Here is an example showing how to make a keymap that inherits 336 Here is an example showing how to make a keymap that inherits
337from @code{text-mode-map}: 337from @code{text-mode-map}:
338 338
339@example 339@example
@@ -342,6 +342,12 @@ from @code{text-mode-map}:
342 map) 342 map)
343@end example 343@end example
344 344
345 A non-sparse keymap can have a parent too, but this is not very
346useful. A non-sparse keymap always specifies something as the binding
347for every numeric character code without modifier bits, even if it is
348@code{nil}, so these character's bindings are never inherited from
349the parent keymap.
350
345@node Prefix Keys 351@node Prefix Keys
346@section Prefix Keys 352@section Prefix Keys
347@cindex prefix key 353@cindex prefix key