From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jason Rumney'" <jasonr@gnu.org>
Cc: 4033@emacsbugs.donarmstrong.com
Subject: bug#4033: 23.1; list-colors-display is misleading
Date: Tue, 4 Aug 2009 16:55:44 -0700 [thread overview]
Message-ID: <EB4BCE79B58B44F7A85D2D8269EC4A55@us.oracle.com> (raw)
In-Reply-To: <4A78C76C.7010001@gnu.org>
> > See my reply to Juri. I'd be grateful for clarification.
> > What's the point of having `display-color-cells' tell me
> > that I have, say 16777216 colors available,
> > if that's not really the case as far as Emacs is concerned?
>
> 16777216 = 2^24 = 2^(3*8): #RRGGBB
= 16^6: 6 hex digits, yes.
OK, so that says that my display only handles 8 bits per component.
But what about this?
> > Doesn't 16-bits per component mean 4 hex digits per component?
> > IOW, #RRRRGGGGBBBB (internally).
IOW, even if my particular display only supports 2 hex digits per component, if
Emacs supports 16 bits per component internally, doesn't that mean that it
supports up to #RRRRGGGGBBBB?
next prev parent reply other threads:[~2009-08-04 23:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 16:01 bug#4033: 23.1; list-colors-display is misleading Drew Adams
2009-08-04 18:04 ` Eli Zaretskii
2009-08-04 18:48 ` Drew Adams
2009-08-04 19:40 ` Drew Adams
2009-08-04 19:45 ` Eli Zaretskii
2009-08-04 19:58 ` Drew Adams
2009-08-04 22:59 ` Jason Rumney
2009-08-04 23:29 ` Drew Adams
2009-08-04 23:42 ` Jason Rumney
2009-08-04 23:55 ` Drew Adams [this message]
2009-08-05 3:22 ` Eli Zaretskii
2009-08-05 5:34 ` Drew Adams
2009-08-05 6:57 ` Jason Rumney
2009-08-05 17:34 ` Eli Zaretskii
2009-08-04 23:27 ` Andreas Schwab
2009-08-04 21:35 ` Juri Linkov
2009-08-04 23:29 ` Drew Adams
2009-08-05 2:25 ` Drew Adams
2009-08-05 2:58 ` Drew Adams
2009-08-05 21:35 ` Juri Linkov
2009-08-05 23:16 ` Drew Adams
2009-08-05 2:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EB4BCE79B58B44F7A85D2D8269EC4A55@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=4033@emacsbugs.donarmstrong.com \
--cc=jasonr@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.