From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: list-colors-display: display all color names
Date: Tue, 04 Jan 2005 23:09:47 +0200 [thread overview]
Message-ID: <01c4f2a1$Blat.v2.2.2$dde14140@zahav.net.il> (raw)
In-Reply-To: <87brc5a99w.fsf@jurta.org> (message from Juri Linkov on Tue, 04 Jan 2005 11:07:55 +0200)
> From: Juri Linkov <juri@jurta.org>
> Date: Tue, 04 Jan 2005 11:07:55 +0200
> Cc: emacs-devel@gnu.org
>
> It's possible to use #RRGGBB hex color specifications instead of
> color names.
Actually, where Emacs interprets such color specs, it uses
#RRRRGGGGBBBB (i.e. 16 bits per color). In other places, it doesn't
care whether you use 1, 2, 3, or 4 hex digits per principal color (it
passes the spec verbatim to X functions).
> it might be difficult for users to obtain corresponding hex values.
How about adding a function color-values-hex, which calls color-values
and then transforms the result into the hex #RGB notation? Would that
fix this problem?
> Also, users might want to find the color name corresponding to
> the known RGB value.
Is there any reasonably practical way to do that for an arbitrary RGB
triplet?
For more-or-less standard RGB values, the ones listed in
tty-colors.el, doing that is simply a matter of searching the alist
returned by tty-color-alist; if trhat is what you want, does this
justify a new feature?
> All I propose now is to add color hex values to the *Colors* buffer.
> I think that placing them at the right window edge would not be
> distracting. For example:
>
> gray grey bebebe
> light gray light grey, LightGray, LightGrey d3d3d3
First, if we do that, I'd suggest to use #BE12BE34BE56, i.e. prefix
with # and use 4 digits per color.
And second, what do you suggest to display on character terminals?
next prev parent reply other threads:[~2005-01-04 21:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 19:45 list-colors-display: display all color names Juri Linkov
2004-12-28 4:57 ` Richard Stallman
2005-01-04 9:07 ` Juri Linkov
2005-01-04 16:37 ` Drew Adams
2005-01-04 21:09 ` Eli Zaretskii [this message]
2005-01-04 21:57 ` Stefan Monnier
2005-01-05 5:38 ` Juri Linkov
2005-01-05 18:12 ` Drew Adams
2005-01-05 19:11 ` Eli Zaretskii
2005-01-05 19:21 ` Edward O'Connor
2005-01-06 4:35 ` Eli Zaretskii
2005-01-05 5:32 ` Juri Linkov
2005-01-05 18:12 ` Drew Adams
2005-01-05 19:13 ` Eli Zaretskii
2005-01-05 18:59 ` Eli Zaretskii
2005-01-05 19:46 ` Drew Adams
2005-01-06 4:50 ` Eli Zaretskii
2005-01-06 8:27 ` Juri Linkov
2005-01-06 9:05 ` Miles Bader
2005-01-06 10:44 ` Juri Linkov
2005-01-05 20:08 ` Richard Stallman
2005-01-05 3:30 ` Richard Stallman
2005-01-06 8:29 ` Juri Linkov
2004-12-29 14:46 ` Michael Mauger
2004-12-29 19:02 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c4f2a1$Blat.v2.2.2$dde14140@zahav.net.il' \
--to=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.