procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update overriding-local-map-menu-flag.

Browse source
This commit is contained in:
Richard M. Stallman 1995-07-18 23:20:50 +00:00
parent 5fe8e44d85
commit 4b4b65a6ca
1 changed files with 15 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
lispref/keymaps.texi
View file

@ -582,21 +582,6 @@ keymap, if any, overrides all other maps that would have been active,
except for the current global map.
@end defvar
@defvar overriding-local-map-menu-flag
If this variable is non-@code{nil}, the value of
@code{overriding-local-map} can affect the display of the menu bar. The
default value is @code{nil}, so @code{overriding-local-map} has no
effect on the menu bar.
Note that @code{overriding-local-map} does affect the execution of key
sequences entered using the menu bar, even if it does not affect the
menu bar display. So if a menu bar key sequence comes in, you should
clear @code{overriding-local-map} before looking up and executing that
key sequence. Modes that use @code{overriding-local-map} would
typically do this anyway; normally they respond to events that they do
not handle by ``unreading'' them and exiting.
@end defvar
@defvar overriding-terminal-local-map
If non-@code{nil}, this variable holds a keymap to use instead of
@code{overriding-local-map}, the buffer's local keymap and all the minor
@ -607,6 +592,21 @@ buffer-local. @xref{Multiple Displays}. It is used to implement
incremental search mode.
@end defvar
@defvar overriding-local-map-menu-flag
If this variable is non-@code{nil}, the value of
@code{overriding-local-map} or @code{overriding-terminal-local-map} can
affect the display of the menu bar. The default value is @code{nil}, so
those map variables have no effect on the menu bar.
Note that these two map variables do affect the execution of key
sequences entered using the menu bar, even if they do not affect the
menu bar display. So if a menu bar key sequence comes in, you should
clear the variables before looking up and executing that key sequence.
Modes that use the variables would typically do this anyway; normally
they respond to events that they do not handle by ``unreading'' them and
exiting.
@end defvar
@node Key Lookup
@section Key Lookup
@cindex key lookup