all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: 37146@debbugs.gnu.org
Subject: bug#37146: 26.2; (elisp) Interactive Codes, for `K'
Date: Thu, 22 Aug 2019 18:30:39 -0700 (PDT)	[thread overview]
Message-ID: <c6495603-46fb-4d09-9b2c-ecd5fa90e08a@default> (raw)
In-Reply-To: <E1i0we0-00051X-1k@fencepost.gnu.org>

> > 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.
> 
> To explain that here would be too much duolication.
> A reference to the Lisp manual would perhaps be worth it.

Yes, that's would be great.  But this _is_ the Lisp
manual.  And I'm not sure the doc to link to exists.
I hope it does, or it will be added.

I guess perhaps the conversions mentioned are those 
described in (elisp) `Key Sequence Input' for function
`read-key-sequence'.  But I'm not sure that's what's
meant.

It's also not clear to me what is meant by "whose
definition you intend to change".  How so?  That seems
to be a description of the ` use case (or main use
case?) of `K' (as opposed to `k'), but it's not clear
to me what that's about.





  reply	other threads:[~2019-08-23  1:30 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 [this message]
2021-06-15 16:35 ` Lars Ingebrigtsen
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c6495603-46fb-4d09-9b2c-ecd5fa90e08a@default \
    --to=drew.adams@oracle.com \
    --cc=37146@debbugs.gnu.org \
    --cc=rms@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.