From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jason Rumney'" <jasonr@gnu.org>, <4033@emacsbugs.donarmstrong.com>
Subject: bug#4033: 23.1; list-colors-display is misleading
Date: Tue, 4 Aug 2009 16:29:55 -0700 [thread overview]
Message-ID: <EFC7E564B9A146DDBE94166A664395F1@us.oracle.com> (raw)
In-Reply-To: <4A78BD5A.8040901@gnu.org>
> >> 16-bit RGB components is what Emacs uses internally, IIRC. That is
> >> the reason we show each one as two letters.
> >
> > Is that right? Could you please check about this?
>
> Emacs uses 16 bit components internally, because that is what
> X uses in its APIs. I'm not aware of any graphics driver that allows
> more than 8 bit granularity though, and on Windows you are restricted
> to 8 bit by the API anyway.
I'm ignorant about these things. Does that imply that Emacs does not support
#RRRRGGGGBBBB (or #RRRGGGBBB) on any systems? What is the relation between these
two
Doesn't 16-bits per component mean 4 hex digits per component? IOW,
#RRRRGGGGBBBB (internally).
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?
Consider me mixed up about this, and please set me straight. Thx.
next prev parent reply other threads:[~2009-08-04 23:29 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 [this message]
2009-08-04 23:42 ` Jason Rumney
2009-08-04 23:55 ` Drew Adams
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
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=EFC7E564B9A146DDBE94166A664395F1@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 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).