GNU bug report logs - #37146
26.2; (elisp) Interactive Codes, for `K'

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Thu, 22 Aug 2019 15:48:02 UTC

Severity: minor

Found in version 26.2

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 37146 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: rms <at> gnu.org
Cc: 37146 <at> debbugs.gnu.org
Subject: RE: bug#37146: 26.2; (elisp) Interactive Codes, for `K'
Date: Thu, 22 Aug 2019 18:30:39 -0700 (PDT)
> > 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.




This bug report was last modified 3 years and 343 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.