summaryrefslogtreecommitdiff
path: root/doc/lispref/keymaps.texi
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2021-12-29 19:30:23 +0200
committerEli Zaretskii <eliz@gnu.org>2021-12-29 19:30:23 +0200
commit1915c19131b5279f65080ec7795761a2e2aa21ea (patch)
treebc911bda99875e3e6f363cc32f1deca74dab68db /doc/lispref/keymaps.texi
parent7715fb3eff59102487e37fba5fc0d421dc8b9a51 (diff)
downloademacs-1915c19131b5279f65080ec7795761a2e2aa21ea.tar.gz
Fix recent changes in 'keymap-lookup' documentation
* doc/lispref/keymaps.texi (Functions for Key Lookup): Improve wording, correct typos.
Diffstat (limited to 'doc/lispref/keymaps.texi')
-rw-r--r--doc/lispref/keymaps.texi9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index 856a1a56717..59cadb021a5 100644
--- a/doc/lispref/keymaps.texi
+++ b/doc/lispref/keymaps.texi
@@ -1240,14 +1240,15 @@ Like the normal command loop, @code{keymap-lookup} will remap the
command resulting from looking up @var{key} by looking up the command
in the current keymaps. However, if the optional third argument
@var{no-remap} is non-@code{nil}, @code{keymap-lookup} returns the
-unmapped command.
+command without remapping.
If the optional argument @var{position} is non-@code{nil}, it
specifies a mouse position as returned by @code{event-start} and
@code{event-end}, and the lookup occurs in the keymaps associated with
-it instead of @var{key}. It can also be a number or marker, in which
-case the keymap properties at the specified buffer position instead of
-point are used.
+that position, instead of in @var{keymap}. @var{position} can also be
+a number or a marker, in which case it is interpreted as a buffer
+position, and the function uses the keymap properties at that position
+instead of at point.
@end defun
@deffn Command undefined