[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 6ae5a59: Clarify (interactive "K") in the manual
From: |
Lars Ingebrigtsen |
Subject: |
master 6ae5a59: Clarify (interactive "K") in the manual |
Date: |
Tue, 15 Jun 2021 12:36:39 -0400 (EDT) |
branch: master
commit 6ae5a59e5275a54a91092ed5c50fe2b42748784a
Author: Lars Ingebrigtsen <larsi@gnus.org>
Commit: Lars Ingebrigtsen <larsi@gnus.org>
Clarify (interactive "K") in the manual
* doc/lispref/commands.texi (Interactive Codes): Clarify
(interactive "K") (bug#37146).
---
doc/lispref/commands.texi | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 8199ece..f30419c 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -454,10 +454,13 @@ This kind of input is used by commands such as
@code{describe-key} and
@code{global-set-key}.
@item K
-A key sequence, whose definition you intend to change. This works like
-@samp{k}, except that it suppresses, for the last input event in the key
-sequence, the conversions that are normally used (when necessary) to
-convert an undefined key into a defined one.
+A key sequence on a form that can be used as input to functions like
+@code{define-key}. This works like @samp{k}, except that it
+suppresses, for the last input event in the key sequence, the
+conversions that are normally used (when necessary) to convert an
+undefined key into a defined one (@pxref{Key Sequence Input}), so this
+form is usually used when prompting for a new key sequence that is to
+be bound to a command.
@item m
@cindex marker argument
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 6ae5a59: Clarify (interactive "K") in the manual,
Lars Ingebrigtsen <=