diff lispref/keymaps.texi @ 51921:86bdb37c1d71

(Functions for Key Lookup): Add current-active-maps. (Scanning Keymaps): Add map-keymaps. (Defining Menus): Add keymap-prompt.

--- a/lispref/keymaps.texi	Mon Jul 14 16:01:20 2003 +0000
+++ b/lispref/keymaps.texi	Mon Jul 14 16:03:04 2003 +0000
@@ -937,6 +937,11 @@
 @end example
 @end defun
 
+@defun current-active-maps
+This returns the list of keymaps that would be used by the command
+loop in the current circumstances to look up a key sequence.
+@end defun
+
 @defun local-key-binding key &optional accept-defaults
 This function returns the binding for @var{key} in the current
 local keymap, or @code{nil} if it is undefined there.
@@ -1473,6 +1478,16 @@
 These are not all the keymaps you would see in actuality.
 @end defun
 
+@defun map-keymap function keymap
+The function @code{map-keymap} calls @var{function} once
+for each binding in @var{keymap}.  It passes two arguments,
+the event type and the value of the binding.  If @var{keymap}
+has a parent, the parent's bindings are included as well.
+
+This function is the cleanest way to examine all the bindings
+in a keymap.
+@end defun
+
 @defun where-is-internal command &optional keymap firstonly noindirect
 This function is a subroutine used by the @code{where-is} command
 (@pxref{Help, , Help, emacs,The GNU Emacs Manual}).  It returns a list
@@ -1573,6 +1588,11 @@
 @code{make-sparse-keymap} or @code{define-prefix-command}
 (@pxref{Creating Keymaps}).
 
+@defun keymap-prompt keymap
+This function returns the overall prompt string of @var{keymap},
+or @code{nil} if it has none.
+@end defun
+
 The order of items in the menu is the same as the order of bindings in
 the keymap.  Since @code{define-key} puts new bindings at the front, you
 should define the menu items starting at the bottom of the menu and