From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 37146@debbugs.gnu.org
Subject: bug#37146: 26.2; (elisp) Interactive Codes, for `K'
Date: Tue, 15 Jun 2021 18:35:03 +0200 [thread overview]
Message-ID: <87fsxjrsqw.fsf@gnus.org> (raw)
In-Reply-To: <dfcc56b9-9f98-435c-801e-c208232948a4@default> (Drew Adams's message of "Thu, 22 Aug 2019 08:45:29 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> This is what it says:
>
> 'K'
> A key sequence, whose definition you intend to change. This works
> like '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.
>
> That's inadequate. In this node you have no idea what "the conversions
> that are normally used (when necessary) to convert an undefined key into
> a defined one" are, or even what that phrase means.
Yes, it's pretty obscure. I've now changed this to the following in
Emacs 28:
@item K
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.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-06-15 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 15:45 bug#37146: 26.2; (elisp) Interactive Codes, for `K' Drew Adams
2019-08-22 23:37 ` Richard Stallman
2019-08-23 1:30 ` Drew Adams
2021-06-15 16:35 ` Lars Ingebrigtsen [this message]
2021-06-15 16:56 ` Eli Zaretskii
2021-06-16 8:15 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsxjrsqw.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37146@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).