From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: julien@danjou.info, simenheg@gmail.com, 24273@debbugs.gnu.org
Subject: bug#24273: 25.1.50; Unexpected return value from `color-name-to-rgb'
Date: Sat, 20 Aug 2016 15:17:52 +0300 [thread overview]
Message-ID: <83fupzd47j.fsf@gnu.org> (raw)
In-Reply-To: <87inuv4par.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 20 Aug 2016 14:07:08 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Simen Heggestøyl <simenheg@gmail.com>,
> julien@danjou.info, 24273@debbugs.gnu.org
> Date: Sat, 20 Aug 2016 14:07:08 +0200
>
> On Aug 20 2016, Eli Zaretskii <eliz@gnu.org> wrote:
>
> >> Date: Sat, 20 Aug 2016 12:11:46 +0200
> >> From: Simen Heggestøyl <simenheg@gmail.com>
> >> Cc: 24273@debbugs.gnu.org
> >>
> >> On Sat, Aug 20, 2016 at 12:06 PM, Julien Danjou <julien@danjou.info>
> >> wrote:
> >> > What are the return values of:
> >> > (color-values "white")
> >> > and
> >> > (color-values "#ffffff")
> >> > ?
> >>
> >> (color-values "white")
> >> ⇒ (65535 65535 65535)
> >>
> >> (color-values "#ffffff")
> >> ⇒ (65280 65280 65280)
> >
> > Which means "white" and "#ffffff" are not the same color.
>
> Actually they are, because #ffffff and #ffffffffffff are the same color
> on a display with 8 bits per color.
I don't think I follow you. What does 8 bits per color have to do
with this, and how do you know the OP has 8 bits per color on his
display?
FWIW, on my display, I get (65535 65535 65535) for both expressions.
next prev parent reply other threads:[~2016-08-20 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 9:47 bug#24273: 25.1.50; Unexpected return value from `color-name-to-rgb' Simen Heggestøyl
2016-08-20 10:06 ` Julien Danjou
2016-08-20 10:11 ` Simen Heggestøyl
2016-08-20 11:34 ` Eli Zaretskii
2016-08-20 12:07 ` Andreas Schwab
2016-08-20 12:17 ` Eli Zaretskii [this message]
2016-08-20 12:32 ` Julien Danjou
2016-08-22 6:12 ` Simen Heggestøyl
2016-08-20 14:23 ` Andreas Schwab
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=83fupzd47j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24273@debbugs.gnu.org \
--cc=julien@danjou.info \
--cc=schwab@linux-m68k.org \
--cc=simenheg@gmail.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.