From 6a0f8bed68b3669fce098382e161ca43ebefe6c2 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Fri, 2 Nov 2001 07:11:18 +0000 Subject: [PATCH] Explain why a parent for a non-sparse keymap is not useful. --- lispref/keymaps.texi | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) 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 -- 2.39.2