From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Face color changes
Date: Sun, 26 Dec 2004 18:49:47 -0500 [thread overview]
Message-ID: <20041226234947.GA13001@fencepost> (raw)
In-Reply-To: <87fz1srfmt.fsf@jurta.org>
On Sun, Dec 26, 2004 at 09:57:38PM +0200, Juri Linkov wrote:
> I noticed that some face colors are bad choices. The worst example
> is "RosyBrown" used for font-lock-string-face on light backgrounds.
> It has high intensity which corresponds to light colors. No wonder
> that this color is hardly visible on light backgrounds.
I'd go farther to say that _many_ of the light-background default faces are
quite pathetically bad; however it's always in my experience been very hard
to form any consensus for change because of the fear that "users will mind"
(not to mention inevitable bickering over what new color to use).
[I use a dark background, so I reserve my energy for keeping those faces sane]
> If this is correct, other face colors could be improved as well
> to match their background mode (i.e. to use light colors on dark
> backgrounds, and dark colors on light backgrounds).
A nice idea, though any such formulaic judgment of color relationships should
be closely scrutinized.
-Miles
--
In New York, most people don't have cars, so if you want to kill a person, you
have to take the subway to their house. And sometimes on the way, the train
is delayed and you get impatient, so you have to kill someone on the subway.
[George Carlin]
next prev parent reply other threads:[~2004-12-26 23:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 19:57 Face color changes Juri Linkov
2004-12-26 23:49 ` Miles Bader [this message]
2004-12-27 8:28 ` Eli Zaretskii
2004-12-27 8:47 ` Jan D.
2004-12-27 22:35 ` Richard Stallman
2004-12-27 8:50 ` Miles Bader
2004-12-27 11:15 ` Eli Zaretskii
2004-12-27 17:16 ` Drew Adams
2004-12-27 17:32 ` Eli Zaretskii
2004-12-27 17:44 ` Drew Adams
2004-12-27 21:49 ` Eli Zaretskii
2004-12-29 7:41 ` Drew Adams
2004-12-29 15:31 ` Alex Schroeder
2004-12-29 19:38 ` Robert J. Chassell
2004-12-29 20:00 ` Robert J. Chassell
2004-12-30 16:43 ` Richard Stallman
2004-12-28 2:52 ` Juri Linkov
2004-12-28 17:25 ` Richard Stallman
2004-12-28 20:16 ` Eli Zaretskii
2004-12-29 4:38 ` Richard Stallman
2004-12-29 5:04 ` Juri Linkov
2004-12-29 15:26 ` Alex Schroeder
2004-12-30 0:22 ` Richard Stallman
2004-12-30 14:18 ` Alex Schroeder
2004-12-30 20:59 ` Richard Stallman
2004-12-30 1:27 ` Miles Bader
2004-12-30 14:15 ` Alex Schroeder
2004-12-30 16:43 ` Richard Stallman
2004-12-30 21:16 ` Miles Bader
2005-01-01 5:24 ` Richard Stallman
2005-01-03 18:17 ` Kevin Rodgers
2005-01-04 3:36 ` Richard Stallman
2005-01-04 9:08 ` Juri Linkov
2004-12-27 22:35 ` Richard Stallman
2004-12-28 2:57 ` Juri Linkov
2004-12-27 18:06 ` Richard Stallman
2004-12-27 8:12 ` Eli Zaretskii
2004-12-28 4:57 ` Richard Stallman
2004-12-28 20:31 ` Eli Zaretskii
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=20041226234947.GA13001@fencepost \
--to=miles@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).