From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 12853@debbugs.gnu.org
Subject: bug#12853: 24.2.50; doc of `color-defined-p'
Date: Sat, 10 Nov 2012 21:17:52 +0200 [thread overview]
Message-ID: <83625dxo67.fsf@gnu.org> (raw)
In-Reply-To: <EDE2EF2A0F5A491292633324D4FE5EE0@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <12853@debbugs.gnu.org>
> Date: Sat, 10 Nov 2012 10:56:04 -0800
>
> I'm asking that the doc be corrected and made more clear and
> complete.
Fine with me. I didn't want to imply that the doc string should not
be corrected. I just wanted to explain why unspecified-* "colors" are
exceptions, and why they are mentioned in the doc string.
> In any case, please make clear here just what is meant by a "defined color" in
> this context
This is already part of the doc string:
Return non-nil if color COLOR is supported on frame FRAME.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Supported" means you can use COLOR in any context where a color is
expected, and the display will show that color without signaling an
error.
> and how that definition relates to those particular noncolor
> defined-color exceptions.
This would require to delve too deep into the internals, which might
not be appropriate for a doc string.
> IOW, if the meaning of "defined color" here were straightforward and we could
> simply point to some other function (e.g. `defined-colors'), then doing that
> would be appropriate and sufficient to make clear what that term means here.
> Since the meaning is NOT obvious or straightforward, it needs to be provided
> (explained).
I don't understand why you are looking for a definition, beyond the
simple one stated in the doc string, when the function we are talking
about, color-defined-p, provides that definition: a "defined color"
for the purposes of this function is something for which this function
returns a non-nil value.
next prev parent reply other threads:[~2012-11-10 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 16:46 bug#12853: 24.2.50; doc of `color-defined-p' Drew Adams
2012-11-10 17:50 ` Eli Zaretskii
2012-11-10 18:12 ` Drew Adams
2012-11-10 18:33 ` Eli Zaretskii
2012-11-10 18:56 ` Drew Adams
2012-11-10 19:17 ` Eli Zaretskii [this message]
2012-11-10 19:51 ` Drew Adams
2012-11-10 20:25 ` Eli Zaretskii
2012-11-23 7:56 ` Chong Yidong
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=83625dxo67.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12853@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).