From: Jason Rumney <jasonr@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 4033@emacsbugs.donarmstrong.com
Subject: bug#4033: 23.1; list-colors-display is misleading
Date: Wed, 05 Aug 2009 14:57:10 +0800 [thread overview]
Message-ID: <4A792D46.2080700@gnu.org> (raw)
In-Reply-To: <33BD7D8E8A9A4543ABDC21D7A5042CEA@us.oracle.com>
Drew Adams wrote:
> The idea then is to have Emacs use an RGB format that is appropriate for the
> user's display. If the display supports 8 bits per component, it would show
> #RRGGBB. If the display supports 16 bits per component, it would show
> #RRRRGGGGBBBB. If the display supports 12 bits per component, it would show
> #RRRGGGBBB.
>
The number of displays supporting more than 8 bits per component is so
miniscule that I don't think it is really worth worrying about. I'm
also not sure what display-color-cells reports on Windows 7 with 30, 36
or 48 bit color output enabled. If it reports anything > 2^24, then it
does not reflect reality, which is that the standard Windows API's do
not support more than 8 bits per component.
next prev parent reply other threads:[~2009-08-05 6:57 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
2009-08-05 3:22 ` Eli Zaretskii
2009-08-05 5:34 ` Drew Adams
2009-08-05 6:57 ` Jason Rumney [this message]
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=4A792D46.2080700@gnu.org \
--to=jasonr@gnu.org \
--cc=4033@emacsbugs.donarmstrong.com \
--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).