From: "Davis Herring" <herring@lanl.gov>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: lekktu@gmail.com, Luc Teirlinck <teirllm@dms.auburn.edu>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Small but confusing doc error in easy-menu-define
Date: Thu, 12 Apr 2007 16:55:42 -0700 (PDT) [thread overview]
Message-ID: <48170.128.165.123.18.1176422142.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <461EB170.1030304@gmail.com>
> It is different level of abstraction, isn't it? Does not "non-nil" in
> Emacs doc usually means that a symbol value is not nil?
Yes, yes it does. In this case, it means that the symbol named "symbol"
(described, as per usual, as SYMBOL in the doc string), which is bound to
the appropriate argument value when the function is called, has a value
that is not nil (and, by implication of the symbol's name ("symbol"), is
some other symbol instead).
Now, if you're talking about the value of the passed symbol as a variable,
I think you'd need to say something to the effect of "If SYMBOL's value as
a variable is non-nil, ...", but that's not what's meant.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2007-04-12 23:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 22:09 Small but confusing doc error in easy-menu-define Lennart Borgman (gmail)
2007-04-12 19:26 ` Stefan Monnier
2007-04-12 19:33 ` Lennart Borgman (gmail)
2007-04-12 19:46 ` Juanma Barranquero
2007-04-12 20:06 ` Lennart Borgman (gmail)
2007-04-12 20:09 ` Luc Teirlinck
2007-04-12 20:19 ` Lennart Borgman (gmail)
2007-04-12 21:46 ` Davis Herring
2007-04-12 22:23 ` Lennart Borgman (gmail)
2007-04-12 23:55 ` Davis Herring [this message]
2007-04-13 12:37 ` Stefan Monnier
2007-04-12 22:03 ` Andreas Schwab
2007-04-12 22:20 ` Lennart Borgman (gmail)
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=48170.128.165.123.18.1176422142.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=teirllm@dms.auburn.edu \
/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).