From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25292@debbugs.gnu.org
Subject: bug#25292: Ambiguity in doc string of defvar
Date: Thu, 29 Dec 2016 19:42:38 +0000 [thread overview]
Message-ID: <20161229194238.GA3387@acm.fritz.box> (raw)
In-Reply-To: <83r34qtwqs.fsf@gnu.org>
Hello, Eli.
On Thu, Dec 29, 2016 at 08:29:15PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 29 Dec 2016 18:18:38 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > INITVALUE is evaluated, and if SYMBOL's value is void, it is used to
> > set SYMBOL. ^^
> That "it" is ambiguous. By default, people tend to interpret "it" as
> referring to the last noun before it, but that's not what you mean in
> this case.
Yes, it's no better than what I was complaining about. :-(
> And after all that, are you sure INITVALUE is always evaluated?
I've had a look at eval.c. INITVALUE is evaluated only when it's going
to be used.
So, maybe the whole paragraph should look like this:
If SYMBOL's value is void and the optional argument INITVALUE is
provided, INITVALUE is evaluated and the result used to set SYMBOL.
If SYMBOL is buffer-local, its default value is what is set;
buffer-local values are not affected. If INITVALUE is missing,
SYMBOL's value is not set.
What do you think?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-12-29 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 18:18 bug#25292: Ambiguity in doc string of defvar Alan Mackenzie
2016-12-29 18:29 ` Eli Zaretskii
2016-12-29 19:42 ` Alan Mackenzie [this message]
2016-12-29 20:35 ` Eli Zaretskii
2016-12-29 20:57 ` Alan Mackenzie
2016-12-30 7:46 ` Eli Zaretskii
2016-12-30 9:02 ` Alan Mackenzie
2016-12-30 9:42 ` Eli Zaretskii
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=20161229194238.GA3387@acm.fritz.box \
--to=acm@muc.de \
--cc=25292@debbugs.gnu.org \
--cc=eliz@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.