From: "Jan D." <jan.h.d@swipnet.se>
Cc: harder@ifa.au.dk, emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: Font-lock.el uses strange value for min-colors (Was x-display-color-cells returns wrong number)
Date: Sun, 29 Feb 2004 20:27:56 +0100 [thread overview]
Message-ID: <60951CF7-6AED-11D8-8672-00039363E640@swipnet.se> (raw)
In-Reply-To: <2914-Sun29Feb2004201424+0200-eliz@elta.co.il>
> 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?
Bad or not, it is the case. An X server is free to use just about any
value
for DisplayCells, it is just the number of cells you get by default
when creating a colormap. In this case, Jesper Harder has 16 planes,
but
just 64 color cells. So he can actually display 65536 colors, not 64.
However, he also has a TrueColor visual, so Emacs should see this and
ignore DisplayCells, I don't know why it doesn't. I see that
list-colors-display has code to ignore DisplayCells for TrueColor
visuals.
It is actually uncommon for any X server to return more than 256 for
DisplayCells, presumably to save memory if a lot of colormaps are
allocated.
A better way to find out the number of colors that can be displayed
at the same time is (1 << DisplayPlanes(...)). There is no need to
distinguish between visual types if number of colors is calculated this
way.
Jan D.
next prev parent reply other threads:[~2004-02-29 19:27 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. [this message]
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
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=60951CF7-6AED-11D8-8672-00039363E640@swipnet.se \
--to=jan.h.d@swipnet.se \
--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).