unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: list-colors-display: display all color names
Date: Wed, 05 Jan 2005 21:11:09 +0200	[thread overview]
Message-ID: <01c4f35a$Blat.v2.2.2$75bad040@zahav.net.il> (raw)
In-Reply-To: <874qhwzb8r.fsf@jurta.org> (message from Juri Linkov on Wed, 05 Jan 2005 07:38:28 +0200)

> From: Juri Linkov <juri@jurta.org>
> Date: Wed, 05 Jan 2005 07:38:28 +0200
> Cc: eliz@gnu.org, emacs-devel@gnu.org
> 
> There is already such a function: `tty-color-approximate' (currently
> it works only for tty colors).

That's because for graphics displays, the same approximation is done
by the C function x_alloc_nearest_color_1.

> I don't know how it is useful from the user's POV.

`tty-color-approximate' is not a user-level function, in general.

> What I intended with adding #RRGGBB values was to make it
> easier for users getting somewhere a #RRGGBB value to see if there is
> a corresponding easily rememberable color name.

How did you think to do that?  I don't think there's a solution for
this problem, since the full set of colors known to the window system
is unknown to Emacs (the colors that are produced by
`list-colors-display' are taken from a partial list that might be only
a tiny fraction of the full list).

> Even better would be if the *Colors* buffer was sorted by RGB values.
> I don't suggest to do that by default, but different sorting order would
> be useful, e.g. by color name, by color intensity.  The latter is good
> for finding a darker or brighter color than a given color, but it is not
> so obvious since there are too many variants of projecting a color value
> from 3-D color space into a 1-D color list.  Perhaps the most useful is
> sorting by hue into a rainbow, and inside every hue sorting by value*saturation.

If we want to add something like that, I'd rather go for a
full-fledged color selection cube, where one can select a color by
moving the mouse pointer, similar to what some X applets let you do.

  parent reply	other threads:[~2005-01-05 19:11 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
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 [this message]
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

  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='01c4f35a$Blat.v2.2.2$75bad040@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 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).