unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <4033@emacsbugs.donarmstrong.com>, "'Eli Zaretskii'" <eliz@gnu.org>
Subject: bug#4033: 23.1; list-colors-display is misleading
Date: Tue, 4 Aug 2009 12:40:32 -0700	[thread overview]
Message-ID: <B7A22BFE895F41EB86047A5292865DFB@us.oracle.com> (raw)
In-Reply-To: <363A8C50DA1A48399649F2A7C5336AD3@us.oracle.com>

> > > 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.
> 
> (I meant #ADADD8D8E6E6 and #ADD8E6 for LightBlue - got my 
> numbers wrong; sorry.)
> 
> > 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?
> 
> I was under the (perhaps mistaken) impression that Emacs treats colors
> differently, depending on your display's color support. In 
> particular, I thought
> that `display-color-cells' would show how many colors are 
> supported, and
> therefore how many RGB hex digits would be appropriate 
> (available) for a given
> display. IOW, I thought that on some displays you might be 
> able to use only
> #RRGGBB, while on others you could use #RRRGGGBBB (where 
> there would be a
> perceived difference when using fewer or more digits).
> 
> > I think this bug should be closed.
> 
> If you're sure about what you say, then yes. But please check 
> to be sure. Thx.

BTW, if what you say is the case, then it is all the more unfortunate, since
`color-values' returns values up to 65535 (or 65280, for some platforms). That's
16 ** 4, which means that each color component can be represented by up to 4 hex
digits: #RRRRGGGGBBBB. That's one reason I've always assumed that up to 4 hex
digits were handled by Emacs.

If what you say is true, then what is the reason for such a limitation? Is there
some inherent limitation, or is this just a design or implementation bug, which
could be fixed?






  reply	other threads:[~2009-08-04 19:40 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 [this message]
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=B7A22BFE895F41EB86047A5292865DFB@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=4033@emacsbugs.donarmstrong.com \
    --cc=eliz@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).