unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: dann@ics.uci.edu, emacs-devel@gnu.org
Subject: Re: face colors on 256 colors terminals
Date: Wed, 06 Apr 2005 20:46:10 +0300	[thread overview]
Message-ID: <01c53ad0$Blat.v2.4$aa0fd4e0@zahav.net.il> (raw)
In-Reply-To: <x53bu3g63o.fsf@lola.goethe.zz> (message from David Kastrup on Wed, 06 Apr 2005 19:36:27 +0200)

> Cc: Dan Nicolaescu <dann@ics.uci.edu>,  emacs-devel@gnu.org
> From: David Kastrup <dak@gnu.org>
> Date: Wed, 06 Apr 2005 19:36:27 +0200
> 
> >        The R, G, and B represent single hexadecimal digits.  When
> >        fewer than 16 bits each are specified, they represent  the
> >        most-significant bits of the value (unlike the "rgb:" syn-
> >        tax, in which values are scaled).  For  example,  #3a7  is
> >        the same as #3000a0007000.
> >
> > So I think the code in tty-colors.el is correct in this matter.  It
> > is, however, possible that the RGB values in color-name-rgb-alist were
> > incorrectly scaled from 8-bit variants, and need to be amended.
> 
> Actually, it does not make sense to scale in that way.  #3a7 really
> should be the same as #3333aaaa7777, so that #fff is the same as
> #ffffffffffff, pure white.

That could be so, but:

 (1) The #RRGGBB syntax being a legacy thingy, I don't believe anyone
     will want to change it; and

 (2) As long as X does it this way, so must we, because when Emacs
     runs on X, the #RRGGBB spec is parsed by the X server, not by
     Emacs (Emacs just hands the spec to X).  If tty-colors.el doesn't
     do _exactly_ the same, a color specified by the same #RRGGBB will
     look differently in an xterm and on X.

  reply	other threads:[~2005-04-06 17:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06  8:17 face colors on 256 colors terminals Dan Nicolaescu
2005-04-06 17:23 ` Eli Zaretskii
2005-04-06 17:36   ` David Kastrup
2005-04-06 17:46     ` Eli Zaretskii [this message]
2005-04-06 18:03       ` David Kastrup
2005-04-06 18:26     ` Dan Nicolaescu
2005-04-07 20:43     ` James Cloos
2005-04-08  1:17       ` Dan Nicolaescu
2005-04-08 10:52         ` Eli Zaretskii
2005-04-08 15:13           ` Dan Nicolaescu
2005-04-09  8:06             ` Eli Zaretskii
2005-04-06 17:52   ` Dan Nicolaescu
     [not found]     ` <01c53aea$Blat.v2.4$16ee4740@zahav.net.il>
2005-04-06 23:50       ` Dan Nicolaescu
2005-04-07  0:22         ` David Kastrup
2005-04-07  3:58           ` Eli Zaretskii
2005-04-07  5:14           ` Dan Nicolaescu
2005-04-07 10:23             ` David Kastrup
2005-04-08  1:13               ` Dan Nicolaescu
2005-04-07  3:55         ` Eli Zaretskii
     [not found]   ` <200504062134.j36LY8AH022227@scanner2.ics.uci.edu>
2005-04-07  3:53     ` Eli Zaretskii
2005-04-07 18:27       ` Dan Nicolaescu
2005-04-08 10:54         ` Eli Zaretskii

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='01c53ad0$Blat.v2.4$aa0fd4e0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@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).