From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Some xterm-256color face colors too bright?
Date: Mon, 31 Jan 2005 21:25:27 +0200 [thread overview]
Message-ID: <01c507ca$Blat.v2.4$c3c54200@zahav.net.il> (raw)
In-Reply-To: <i56u0oxeogg.fsf@shaka.acc.umu.se> (message from stktrc on Mon, 31 Jan 2005 15:07:59 +0200)
> From: stktrc <stktrc@yahoo.com>
> Date: Mon, 31 Jan 2005 15:07:59 +0200
>
> The default colors of some faces become very bright, bordering on
> too bright to be readable, when using an xterm-256color terminal
> with light background (correctly detect in frame-background-mode).
> Such faces are for example font-lock-string-face and
> compilation-warning-face.
If you type "M-x customize-face RET font-lock-string-face RET", what
color name do you see in the Custom buffer?
The default color for that face on light-background displays with more
than 88 colors is "RosyBrown". I cannot see how this could be so
bright as to annoy you. Could it be that the background color is
actually the problem (Emacs doesn't touch the background color in a
non-windowed session, it uses the color that it found)?
You might also start a windowed Emacs session with a light background
and compare the colors for that face in the two sessions, both for
background and foreground colors. If you do that, what do you see?
> I guess that this is not related to the individual face selections,
> but rather to the algorithm by which colors are mapped onto XTerms
> colors. Any hints on which parts of Emacs to look in to tune this?
The code that does it is in lisp/term/xterm.el. But I don't think
that code is to blame: all it does is register the 256 colors with
their RGB values, which cannot possibly cause such problems.
next parent reply other threads:[~2005-01-31 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <i56u0oxeogg.fsf@shaka.acc.umu.se>
2005-01-31 19:25 ` Eli Zaretskii [this message]
2005-01-31 20:22 ` Some xterm-256color face colors too bright? Luc Teirlinck
2005-02-01 4:36 ` Eli Zaretskii
[not found] ` <i56oef48pr2.fsf@shaka.acc.umu.se>
2005-02-01 19:52 ` Eli Zaretskii
2005-02-01 20:21 ` Stefan Monnier
[not found] ` <i564qgwvul2.fsf@shaka.acc.umu.se>
2005-02-02 1:06 ` Stefan Monnier
2005-02-02 1:21 ` Miles Bader
2005-02-02 4:37 ` Eli Zaretskii
[not found] ` <i56brb32wtm.fsf@shaka.acc.umu.se>
2005-02-02 18:04 ` Eli Zaretskii
2005-02-03 6:39 ` Richard Stallman
2005-02-01 20:56 ` David Hansen
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='01c507ca$Blat.v2.4$c3c54200@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).