From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, 4033@emacsbugs.donarmstrong.com
Subject: bug#4033: 23.1; list-colors-display is misleading
Date: Tue, 04 Aug 2009 21:04:35 +0300 [thread overview]
Message-ID: <83r5vro3po.fsf@gnu.org> (raw)
In-Reply-To: <4B9B03BEE43E44B79206302B26E01B3A@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Tue, 4 Aug 2009 09:01:21 -0700
> Cc:
>
> emacs -Q
> M-x list-colors-display
>
> The RGB values listed at the right side are misleading.
Only if you interpret them to mean not what they were supposed to
mean.
> The displayed RGB hex string ideally should reflect the user's actual
> color possibilities. If there is no way for Emacs to know that, then
> it's better to err on the side of providing more information:
> #RRRRGGGGBBBB, rather than less: #RRGGBB. E.g., it's better to
> translate LightBlue as #befded5effff than as #beedff.
16-bit RGB components is what Emacs uses internally, IIRC. That is
the reason we show each one as two letters.
I think this bug should be closed.
next prev parent reply other threads:[~2009-08-04 18:04 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 [this message]
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
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=83r5vro3po.fsf@gnu.org \
--to=eliz@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).