Explain why a parent for a non-sparse keymap is not useful.
This commit is contained in:
parent
998d7b3bf6
commit
6a0f8bed68
1 changed files with 7 additions and 1 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue