unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 'Bastien' <bzg@altern.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: RE: highlight failed part of isearch input
Date: Sat, 23 Feb 2008 15:12:44 -0800	[thread overview]
Message-ID: <003801c87671$9926fbb0$0600a8c0@us.oracle.com> (raw)
In-Reply-To: <87fxvjmj7c.fsf@jurta.org>

> > Personally, I disagree about the color, at least for a 
> > light background with unlimited colors available - it
> > is too vivid (bright, saturated, loud). For that,
> > Plum or some other pastel is a better default, IMO.
> 
> Plum is too washed-out and weak color to indicate the error.

OK, we disagree. Maybe others, besides we two, have an opinion?

I think we want a washed-out color (Plum or another) to indicate this
"error". It should scarcely be noticeable, and it should certainly not be
distracting.

This is not about signaling some fatal error, it is about indicating a
typing mistake. I doubt most people want sirens to go off to alert them of
such a typo.

> > It's important to not only notice the failure but also 
> > easily read the text that is highlighted.
> 
> The failed search string on IndianRed1 is quite readable on a light
> background as well as on a dark background.

Again, let's try to get some more opinions on this. To me, this highlighting
should be only a subtle help - it shouldn't get in the way. And I don't find
black text on IndianRed1 to be very readable.

> > For a dark background, the color should presumably be quite 
> > dark, not bright.
> >
> > Also, I think it should specify a foreground color by 
> > default, for the case where someone uses a different
> > foreground color for a standalone minibuffer.
> 
> I think it is better to use the default foreground color,
> and if it is unreadable then the user can customize it
> to some other color that fits to user's color theme.

OK. 

But all the more reason, then, not to use the same highlight color for light
and dark background displays. And all the more reason for the highlight
color to not vary too much in value (brightness) from the default background
in each case. A pastel highlight is good for a light background, and a
darkish highlight is good for a dark background.

I don't care which hue we choose, but pastel for light background and
darkish for dark background is important, I think. We should stay away from
mid-range values.

> > How about something like this? The default color here for a 
> > dark background is the complement of Plum (a light violet):
> > a dark green. You certainly don't want something like
> > IndianRed1 or Plum on a dark background, I expect.
> 
> I'm not against selecting a more suitable color on a dark
> background, but a dark green definitely doesn't fit
> semantically and is unnoticeable.

Semantically? Do you mean fire-engine red as in "EMERGENCY!" vs green as in
"Go, it's agreen light?" ;-)

Looking for semantics in the color used here is stretching it. Better to
just look for something that works visually: dark enough, but not too dark,
etc. 

I don't care which hue (green, red, blue, magenta, cyan, yellow) we use, but
the difference in value (brightness) from the normal background should be
slight - noticeable, but slight.

> > BTW - I'm no expert on face specs, but isn't your 
> > duplication of the red spec for (min-colors 8) and
> > (min-colors 16) redundant? Doesn't (min-colors 8),
> > as shown above, take care of both?
> 
> I don't know a reason for this duplication.  I took the 
> definition from the `isearch' face that has this duplication.

Hm. Maybe someone who is wise in these things can light our lanterns.





  reply	other threads:[~2008-02-23 23:12 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10  3:03 highlight failed part of isearch input Drew Adams
2007-07-10 13:21 ` Juri Linkov
2007-07-10 14:19   ` Drew Adams
2007-07-10 23:22     ` Juri Linkov
2007-07-11  0:16       ` Drew Adams
2007-07-11  3:57         ` Stefan Monnier
2007-07-11  5:27           ` David Kastrup
2007-07-11  6:18             ` Stefan Monnier
2007-07-11  6:26               ` Miles Bader
2007-07-11  7:14                 ` Stefan Monnier
2007-07-11  7:15                 ` David Kastrup
2007-07-11 16:10           ` Drew Adams
2007-07-11 19:20             ` Robert J. Chassell
2007-07-11 21:14               ` Drew Adams
2007-07-11 23:17                 ` Juri Linkov
2007-07-12 13:01                 ` Robert J. Chassell
     [not found]                 ` <E1I968h-0002xA-VO@fencepost.gnu.org>
2007-07-12 23:16                   ` Juri Linkov
2007-07-13 18:38                     ` Richard Stallman
2007-07-14 23:05                       ` Juri Linkov
2007-07-15 22:53                         ` Richard Stallman
2007-07-23  4:27                         ` Richard Stallman
2007-07-14 23:07                       ` Juri Linkov
2007-07-15 22:53                         ` Richard Stallman
2007-07-12 21:24             ` Richard Stallman
2007-07-11 21:03       ` Richard Stallman
2007-07-11 21:15         ` Drew Adams
2007-07-10 14:07 ` Masatake YAMATO
2007-07-10 14:37   ` ding susceptibility (was: highlight failed part of isearch input) Drew Adams
2007-07-10 22:01   ` highlight failed part of isearch input Richard Stallman
2007-07-10 14:32 ` Stefan Monnier
2007-07-10 22:01 ` Richard Stallman
2007-07-22 23:40   ` Drew Adams
2007-07-23 18:06     ` Richard Stallman
2007-07-23 21:29       ` Juri Linkov
2007-07-23 22:37         ` Drew Adams
2007-07-23 23:33           ` Juri Linkov
2007-07-24  2:22             ` Drew Adams
2007-07-24 22:16               ` Richard Stallman
2007-07-24 16:45         ` Richard Stallman
2007-07-24 17:25           ` Drew Adams
2008-02-11 23:31       ` Drew Adams
2008-02-12  0:18         ` Juri Linkov
2008-02-12  0:36           ` Drew Adams
2008-02-12  0:54             ` Bastien
2008-02-16 19:18               ` Juri Linkov
2008-02-23 19:47                 ` Juri Linkov
2008-02-23 21:27                   ` Drew Adams
2008-02-23 21:55                     ` Juri Linkov
2008-02-23 23:12                       ` Drew Adams [this message]
2008-02-24 17:32                         ` Juri Linkov
2008-02-24 23:15                           ` Drew Adams
2008-02-25  0:01                             ` Juri Linkov
2008-02-25  7:59                             ` Bastien
2008-02-24 23:31                           ` Dan Nicolaescu
2008-02-24 23:47                             ` Drew Adams
2008-02-24 23:58                               ` Dan Nicolaescu
2008-02-25  0:00                               ` Jason Rumney
2008-02-25  0:12                                 ` Drew Adams
2008-02-25  0:17                                 ` Juri Linkov
2008-02-24 17:29                   ` Juri Linkov
2008-02-24 23:05                     ` Drew Adams

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='003801c87671$9926fbb0$0600a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=bzg@altern.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@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).