all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 14199@debbugs.gnu.org
Subject: bug#14199: 24.3.50; `read-kbd-macro' doc
Date: Sat, 08 Feb 2014 04:33:02 -0800	[thread overview]
Message-ID: <87lhxlss1t.fsf@building.gnus.org> (raw)
In-Reply-To: <7A6B3EA5F62D48D291D7E316EF83AB17@us.oracle.com> (Drew Adams's message of "Sat, 13 Apr 2013 10:49:04 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> In (elisp) `Describing Characters', description of `read-kbd-macro':
>
> 1. The signature and description are incorrect/incomplete.  According to
> the source code and the doc string, the signature is (read-kbd-macro
> START &optional END).
>
> The doc string shows the correct signature, and it is clearer than
> the manual wrt the signature and the possibility of passing STRING
> and NEED-VECTOR instead.
>
> The manual needs to clearly point out that there are, in effect, two
> different signatures, even if one is considered primary.  Each needs
> to be documented.

The region-based interactive definition is documented in the Emacs
manual, while the Lisp-based is in the lispref manual.  I think that's
probably ok, while it does seem pretty strange to reuse the meanings of
the parameters.

> 2. Mention that STRING has the form provided by `format-kbd-macro'.
> `format-kbd-macro' is mentioned nowhere in the manual, and this is a
> good place for it.

Well, it mentions that it's an inverse of `key-description', which
should cover it...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2014-02-08 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 17:49 bug#14199: 24.3.50; `read-kbd-macro' doc Drew Adams
2014-02-08 12:33 ` Lars Ingebrigtsen [this message]
2014-02-10 22:00   ` Drew Adams

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=87lhxlss1t.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=14199@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 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.