From: Juri Linkov <juri@jurta.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 'David Koppelman' <koppel@ece.lsu.edu>, 13686@debbugs.gnu.org
Subject: bug#13686: hi-yellow vs. hi-lock-1
Date: Thu, 07 Mar 2013 11:16:05 +0200 [thread overview]
Message-ID: <87d2vbmuzq.fsf@mail.jurta.org> (raw)
In-Reply-To: <871ubsz7wr.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 07 Mar 2013 00:13:00 +0530")
>> `hi-yellow' is a meaningful name. Together with other complementary
>> faces they cover the whole color space.
>
> It is difficult for me to believe that the original design intent was to
> "cover color space".
>
> hi-black-b
> hi-black-hb
> hi-blue
> hi-blue-b
> hi-green
> hi-green-b
> hi-pink
> hi-red-b
> hi-yellow
>
> You see there are two blacks, two blues and two greens. Try
>
> C-u M-x list-colors-display RET hi- RET
>
> and convince yourself how close or far away it is from covering the
> whole "color space". It seems like a mixed bag. If there is a design,
> I am not seeing it.
When I try `C-u M-x list-faces-display RET hi- RET'
I see exactly the same colors as displayed in the first image
in http://en.wikipedia.org/wiki/RGB
Primary colors: hi-red-b, hi-green-b, hi-blue-b.
Secondary colors: hi-blue, hi-pink, hi-yellow.
So there is a complete coverage of the colors
evenly distributed on the color wheel.
next prev parent reply other threads:[~2013-03-07 9:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 6:14 bug#13686: 24.3.50; Re-look hi-lock-face-defaults (aka Provide more "core" faces for highlighting) Jambunathan K
2013-02-15 15:03 ` Stefan Monnier
2013-02-15 18:29 ` David Koppelman
2013-02-15 20:39 ` Stefan Monnier
2013-02-26 23:11 ` bug#13686: hi-yellow vs. hi-lock-1 David Koppelman
2013-02-27 0:33 ` Drew Adams
2013-02-27 1:35 ` Stefan Monnier
2013-02-27 3:59 ` Jambunathan K
2013-02-27 4:58 ` Drew Adams
2013-02-27 5:10 ` Jambunathan K
2013-02-27 5:38 ` Drew Adams
2013-02-27 5:54 ` Jambunathan K
2013-02-27 6:01 ` Drew Adams
2013-02-27 23:45 ` Juri Linkov
2013-03-06 18:43 ` Jambunathan K
2013-03-06 19:54 ` David Koppelman
2013-03-07 9:16 ` Juri Linkov [this message]
2013-03-06 19:04 ` Jambunathan K
2013-02-27 3:49 ` Jambunathan K
2013-02-27 13:46 ` Stefan Monnier
2013-02-27 14:56 ` Jambunathan K
2013-02-27 16:27 ` Stefan Monnier
2013-03-06 18:56 ` Jambunathan K
2013-03-06 19:55 ` David Koppelman
2013-03-06 20:06 ` Jambunathan K
2013-03-07 0:54 ` David Koppelman
2013-03-07 3:23 ` Jambunathan K
2013-03-09 1:33 ` Stefan Monnier
2013-03-09 2:47 ` Jambunathan K
2013-03-09 3:26 ` Stefan Monnier
2013-04-08 5:31 ` Jambunathan K
2013-04-10 4:11 ` Jambunathan K
2013-04-10 18:33 ` David Koppelman
2013-04-11 4:24 ` Jambunathan K
2013-02-27 3:36 ` Jambunathan K
2013-02-27 4:08 ` Jambunathan K
2013-11-15 4:45 ` bug#13686: 24.3.50; Re-look hi-lock-face-defaults (aka Provide more "core" faces for highlighting) Jambunathan K
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=87d2vbmuzq.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=13686@debbugs.gnu.org \
--cc=kjambunathan@gmail.com \
--cc=koppel@ece.lsu.edu \
/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).