bug#2454: marked as done (23.0.90; Colored Compilation Status is hard on the eyes)

[owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)]

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]


Your message dated Wed, 25 Feb 2009 09:50:41 -0800 (PST)
with message-id <200902251750.n1PHofPD012730@rodan.ics.uci.edu>
and subject line Re: bug#2454: 23.0.90; Colored Compilation Status is hard on the eyes
has caused the Emacs bug report #2454,
regarding 23.0.90; Colored Compilation Status is hard on the eyes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
2454: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2454
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 9019 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 1613 bytes --]

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.



  -- MJF





In GNU Emacs 23.0.90.1 (i386-mingw-nt5.1.2600)

 of 2009-02-01 on SOFT-MJASON

Windowing system distributor `Microsoft Corp.', version 5.1.2600

configured using `configure --with-gcc (3.4)'



Important settings:

  value of $LC_ALL: nil

  value of $LC_COLLATE: nil

  value of $LC_CTYPE: nil

  value of $LC_MESSAGES: nil

  value of $LC_MONETARY: nil

  value of $LC_NUMERIC: nil

  value of $LC_TIME: nil

  value of $LANG: ENU

  value of $XMODIFIERS: nil

  locale-coding-system: cp1252

  default-enable-multibyte-characters: t



Major mode: Grep



Minor modes in effect:

  tooltip-mode: t

  tool-bar-mode: t

  mouse-wheel-mode: t

  menu-bar-mode: t

  file-name-shadow-mode: t

  global-font-lock-mode: t

  font-lock-mode: t

  blink-cursor-mode: t

  global-auto-composition-mode: t

  auto-composition-mode: t

  auto-encryption-mode: t

  auto-compression-mode: t

  line-number-mode: t

  transient-mark-mode: t



Recent input:

<help-echo> <apps> <apps> M-x r g r e p <return> t

e s t <return> <return> ~ / <tab> <return> <down-mouse-1>

<mouse-1> <help-echo> <help-echo> <help-echo> <help-echo>

<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>

<help-echo> <menu-bar> <help-menu> <send-emacs-bug

-report>



Recent messages:

For information about GNU Emacs and the GNU system, type C-h C-a.

[-- Attachment #2.1.2: Type: text/html, Size: 4633 bytes --]

[-- Attachment #3: Type: message/rfc822, Size: 3825 bytes --]

From: Dan Nicolaescu <dann@ics.uci.edu>
To: Juri Linkov <juri@jurta.org>
Cc: Jared Finder <jfinder@crypticstudios.com>, 2454-done@emacsbugs.donarmstrong.com
Subject: Re: bug#2454: 23.0.90; Colored Compilation Status is hard on the eyes
Date: Wed, 25 Feb 2009 09:50:41 -0800 (PST)
Message-ID: <200902251750.n1PHofPD012730@rodan.ics.uci.edu>

Juri Linkov <juri@jurta.org> writes:

  > > 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.

Colors are something that absolutely impossible to get everyone to agree on.
The code in question has been in CVS for one year, many people have said
they liked it.  
Now we got one person that does not.
This is about as good of a consensus on colors that we can get.

Plus, given that the faces are used to highlight <10 characters in the
mode-line, and the text is always the same.  The only thing that matters
is the color.  
Users don't need to read the text as soon as they recognize the color:
red -- an error, green -- great, it worked.
This feature was implemented using already defined faces, adding new
faces for something just in that modeline is not worth it.

All this being said, this is not a bug, so I am going to close it.


  > Or maybe using a light background (white) for these messages in the
  > mode-line, i.e. to use exacly the same default foreground/background
  > they currently have in a compilation/grep buffer.

That would be even more controversial, we don't have anything else in
the mode-line that uses the default foreground.