From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 13571@debbugs.gnu.org
Subject: bug#13571: 24.3.50; doc of `interactive'
Date: Fri, 29 Apr 2016 00:23:07 +0200 [thread overview]
Message-ID: <871t5p4blg.fsf@gnus.org> (raw)
In-Reply-To: <6B1C0A2C1FE74926A90E8BEFA7562DF4@us.oracle.com> (Drew Adams's message of "Sun, 27 Jan 2013 18:21:48 -0800")
"Drew Adams" <drew.adams@oracle.com> writes:
> 1. For `v' it should not say "Variable name", even if it also mentions
> `custom-variable-p'. It should speak of "option", not "variable". E.g.:
>
> Option: a symbol that is `custom-variable-p'. The name is read.
>
> A user should not need to click `custom-variable-p', or be already
> familiar with that Lisp predicate, to understand that this reads
> an option name, not the name of an arbitrary variable.
I disagree. Saying that it's a variable helps with understanding here.
> 2. There is confusion in the doc string and in (elisp) `Interactive Codes'
> regarding (a) what a given interactive code reads and (b) what value it
> returns/provides for the argument.
>
> In particular, we misleadingly see mention of "name" here and there.
>
> A name is read in such cases, but a name, i.e., a string, is not always what is
> returned. In many cases, a symbol is returned. A symbol is a special Lisp
> object, and definitely not a name. It has a name, as well as other properties.
>
> Some of the entries, such as `b', are correct: they read and return a name, not
> the object named (e.g. a buffer).
>
> The following entries incorrectly speak of "name". They read names, but they
> return symbols, and the doc is not clear about this.
>
> a
> C
> v
> z
> Z
All these say that are symbols, and I think that's clear enough.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-28 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 2:21 bug#13571: 24.3.50; doc of `interactive' Drew Adams
2016-04-28 22:23 ` Lars Ingebrigtsen [this message]
2016-04-29 16: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
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=871t5p4blg.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=13571@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).