From: Jared Finder <jfinder@crypticstudios.com>
To: "'Dan Nicolaescu'" <dann@ics.uci.edu>
Cc: "2454@emacsbugs.donarmstrong.com" <2454@emacsbugs.donarmstrong.com>
Subject: bug#2454: 23.0.90; Colored Compilation Status is hard on the eyes
Date: Tue, 24 Feb 2009 10:10:49 -0800 [thread overview]
Message-ID: <C73CE12E0E2E6D4AA8C97475050023A60FF1A61CBE@proserpine.paragon.crypticstudios.com> (raw)
In-Reply-To: <200902240231.n1O2VhH3007810@rodan.ics.uci.edu>
Sure.
I'm referring to the color used by the compilation status in the mode line (one of :exit[0], :exit[SOMETHING ELSE], or :run). The orange and green used here hurt. The red is passable, but still not good.
I believe the mode-line and mode-line inactive faces contribute the background color and compilation-error, compilation-warning, and compilation-info contribute the foreground color. The problem is that they don't contrast well with the mode-line's default bg colors. Orange on Gray75 hurts my eyes, as does Green3 on Gray75, or Red1 on Gray75.
I'd suggest using darker foreground colors, so they don't hurt my eyes.
-- MJF
-----Original Message-----
From: Dan Nicolaescu [mailto:dann@ics.uci.edu]
Sent: Monday, February 23, 2009 6:32 PM
To: Jared Finder
Cc: 2454@emacsbugs.donarmstrong.com
Subject: Re: bug#2454: 23.0.90; Colored Compilation Status is hard on the eyes
Jared Finder <jfinder@crypticstudios.com> writes:
> The colors chosen for the compilation status are very hard on the eyes with the
> default mode-line colors. Please change the compilation status to use darker
> colors.
Can you please explain what do you mean?
If you are talking about the color used to display "error" in case there
was a compilation error, that color is loud by design.
next prev parent reply other threads:[~2009-02-24 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200902251750.n1PHofPD012730@rodan.ics.uci.edu>
2009-02-24 1:17 ` bug#2454: 23.0.90; Colored Compilation Status is hard on the eyes Jared Finder
2009-02-24 2:31 ` Dan Nicolaescu
2009-02-24 18:10 ` Jared Finder [this message]
2009-02-24 20:04 ` Juri Linkov
2009-02-25 17:55 ` bug#2454: marked as done (23.0.90; Colored Compilation Status is hard on the eyes) Emacs bug Tracking System
[not found] ` <handler.2454.D2454.123558425721593.notifdone@emacsbugs.donarmstrong.com>
2009-02-25 18:25 ` bug#2454: closed by Dan Nicolaescu <dann@ics.uci.edu> (Re: bug#2454: 23.0.90; " Jared Finder
2009-02-25 21:45 ` bug#2454: 23.0.90; Colored Compilation Status is hard on the eyes Juri Linkov
2009-02-25 21:47 ` Jared Finder
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=C73CE12E0E2E6D4AA8C97475050023A60FF1A61CBE@proserpine.paragon.crypticstudios.com \
--to=jfinder@crypticstudios.com \
--cc=2454@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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).