From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: harder@ifa.au.dk, emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: Font-lock.el uses strange value for min-colors (Was x-display-color-cells returns wrong number)
Date: Mon, 01 Mar 2004 08:00:15 +0200 [thread overview]
Message-ID: <7494-Mon01Mar2004080015+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040229220341.GA9343@fencepost> (message from Miles Bader on Sun, 29 Feb 2004 17:03:41 -0500)
> Date: Sun, 29 Feb 2004 17:03:41 -0500
> From: Miles Bader <miles@gnu.org>
>
> On Sun, Feb 29, 2004 at 08:14:24PM +0200, Eli Zaretskii wrote:
> > However, this sounds like a tip of an iceberg: are you saying that
> > list-display-colors will display a list whose length has no simple
> > relation to what display-color-cells returns? That sounds bad,
> > doesn't it?
>
> Um, no. [I presume you meant `list-colors-display',]
Yes, sorry for the typo.
> Perhaps the doc string should be more clear about it [though I suppose
> technically it's accurate, as it makes no mention of being exhaustive], but
> the default behavior on X is to display a list of `interesting' colors (those
> with names). Such a list is more likely to emphasize colors that are
> interesting to human eyes, and I doubt that anyone cares whether such it has
> any simple relationship to the number of possible colors when its length is
> above about a 100 or so -- you can still, obviously, use the #xxx notation to
> get any color you want.
I know that the list of colors displayed by list-colors-display on X
is fixed (see my message earlier in this thread), but I always
thought, I don't know why, that the length of that list is near the
number returned by display-color-cells.
If this is not true, one may ask what is so ``interesting'' about the
specific colors we show as opposed to those we don't. For example,
when I work on Irix, I generally like to use the Irix-specific colors
(that are not shown by list-colors-display, of course) because they
are much more pleasant to my eyes. So to me, those unshown colors are
much more ``interesting'' than those we show, in that specific case.
The importance of list-colors-display is that some people use it to
choose colors for their customizations, so the shown colors need to
have some resemblance to what Emacs can support.
Bottom line is, I think list-colors-display should display colors
whose number is close to what Emacs can use on that display, except
that it probably shouldn't be too long (so I don't suggest to display
64K colors, for example). Perhaps a short comment to the effect that
we are showing only N out of possible M colors would be good there.
But this is not the gravest problem with this issue; see my other
messages about the value returned by display-color-cells, which I
think is the main issue here.
next prev parent reply other threads:[~2004-03-01 6:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3eksf9sq6.fsf@defun.localdomain>
[not found] ` <14AB9AB8-6A0E-11D8-99DB-00039363E640@swipnet.se>
[not found] ` <m3d67z84rb.fsf@defun.localdomain>
2004-02-29 17:01 ` Font-lock.el uses strange value for min-colors (Was x-display-color-cells returns wrong number) Jan D.
2004-02-29 18:14 ` Eli Zaretskii
2004-02-29 19:27 ` Jan D.
2004-02-29 21:25 ` Eli Zaretskii
2004-02-29 21:58 ` Jan D.
2004-03-01 5:50 ` Eli Zaretskii
2004-03-01 12:55 ` Jan D.
2004-02-29 22:39 ` Jason Rumney
2004-03-01 6:07 ` Eli Zaretskii
2004-03-01 8:30 ` Jason Rumney
2004-03-01 19:51 ` Eli Zaretskii
2004-02-29 22:03 ` Miles Bader
2004-03-01 6:00 ` Eli Zaretskii [this message]
2004-03-01 6:24 ` Miles Bader
2004-03-01 19:55 ` Eli Zaretskii
2004-03-02 2:24 ` Miles Bader
2004-03-02 5:47 ` Eli Zaretskii
2004-03-02 6:33 ` Miles Bader
2004-03-01 9:39 ` Jan D.
2004-02-29 18:18 ` Font-lock.el uses strange value for min-colors Jesper Harder
2004-02-29 21:22 ` Eli Zaretskii
2004-02-29 18:54 ` Font-lock.el uses strange value for min-colors (Was x-display-color-cells returns wrong number) Luc Teirlinck
2004-02-29 19:33 ` Jan D.
2004-02-29 20:07 ` Luc Teirlinck
2004-02-29 20:20 ` Jan D.
2004-02-29 21:29 ` Luc Teirlinck
2004-03-01 10:47 ` Kim F. Storm
2004-03-01 12:11 ` Richard Stallman
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=7494-Mon01Mar2004080015+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=harder@ifa.au.dk \
/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).