From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-pretest-bug@gnu.org, emacs-devel Devel <emacs-devel@gnu.org>
Subject: Font-lock.el uses strange value for min-colors (Was x-display-color-cells returns wrong number)
Date: Sun, 29 Feb 2004 18:01:09 +0100 [thread overview]
Message-ID: <DEFB56DC-6AD8-11D8-848D-00039363E640@swipnet.se> (raw)
In-Reply-To: <m3d67z84rb.fsf@defun.localdomain>
> "Jan D." <jan.h.d@swipnet.se> writes:
>
>>> (x-display-color-cells) => 64
>>>
>>> I noticed because of the recent change in font-lock.el -- since
>>> 64 < 88 I now get really ugly font-lock colours.
>>
>> This function does not look to have been changed for a very long time.
>> It basically just returns
>> DisplayCells (dpyinfo->display,
>> XScreenNumberOfScreen (dpyinfo->screen))
>>
>> Have you changed X server lately?
>
> No. `x-display-color-cells' has probably always returned 64 (it also
> does that in Emacs 21.3), but I guess it just wasn't used anywhere
> important before now.
Well, looking at your xdpyinfo, the only thing it can return is 64.
But this is not the problem you have. What you are saying is that
64 works fine as a value for min-colors in font-lock.el instead of
88. Your problem has nothing to do with x-display-color-cells.
88 is a funny value, I don't know how that value was reached, Cc:ing
emacs-devel to see if anybody can help.
Jan D.
next parent reply other threads:[~2004-02-29 17:01 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 ` Jan D. [this message]
2004-02-29 18:14 ` Font-lock.el uses strange value for min-colors (Was x-display-color-cells returns wrong number) 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
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=DEFB56DC-6AD8-11D8-848D-00039363E640@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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).