[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 1915c19131: Fix recent changes in 'keymap-lookup' documentation
From: |
Eli Zaretskii |
Subject: |
master 1915c19131: Fix recent changes in 'keymap-lookup' documentation |
Date: |
Wed, 29 Dec 2021 12:30:40 -0500 (EST) |
branch: master
commit 1915c19131b5279f65080ec7795761a2e2aa21ea
Author: Eli Zaretskii <eliz@gnu.org>
Commit: Eli Zaretskii <eliz@gnu.org>
Fix recent changes in 'keymap-lookup' documentation
* doc/lispref/keymaps.texi (Functions for Key Lookup): Improve
wording, correct typos.
---
doc/lispref/keymaps.texi | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index 856a1a5671..59cadb021a 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 1915c19131: Fix recent changes in 'keymap-lookup' documentation,
Eli Zaretskii <=