From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>, "'Bastien'" <bzg@altern.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: RE: highlight failed part of isearch input
Date: Sat, 23 Feb 2008 13:27:57 -0800 [thread overview]
Message-ID: <003001c87662$f62a0280$0600a8c0@us.oracle.com> (raw)
In-Reply-To: <8763wfpi9w.fsf@jurta.org>
> The patch below fixes this problem. When the first message from the
> isearch-cmds stack is not the same as isearch-message (this
> happens when isearch-edit-string sets a different value) then it
> uses this value for succ-msg.
Thanks; good catch.
> Also this patch uses a better background color for the
> `isearch-fail' face - the same color as used by Firefox
> for the background of the failed search text. UI designers
> of Firefox made a good job and this color looks nice.
How about separating that face-change suggestion, which is independent of
the bug fix?
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. It's important to
not only notice the failure but also easily read the text that is
highlighted.
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.
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.
(defface isearch-fail
'((((class color) (min-colors 88) (background dark))
(:foreground "white" :background "#22225F5F2222"))
(((class color) (min-colors 88) (background light))
(:foreground "Black" :background "Plum"))
(((class color) (min-colors 8)) (:background "red"))
(((type tty) (class mono)) :inverse-video t)
(t :background "gray"))
"Face for highlighting failed part in Isearch echo-area message."
:version "23.1" :group 'isearch)
I also added the mono case and the catch-all case. Copied them from the
definition for `region'.
I can't speak much to what should be the default for a dark background or
for when there are limited colors available. Perhaps people who use those
contexts could suggest an improvement.
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?
> ! (defface isearch-fail '((t (:foreground "Black" :background
> "Plum")))
> "Face for highlighting failed part in Isearch echo-area message."
> :group 'isearch)
>
> (defcustom isearch-lazy-highlight t
> --- 231,245 ----
> :group 'basic-faces)
> (defvar isearch 'isearch)
>
> ! (defface isearch-fail
> ! '((((class color) (min-colors 88))
> ! (:background "IndianRed1"))
> ! (((class color) (min-colors 16))
> ! (:background "red"))
> ! (((class color) (min-colors 8))
> ! (:background "red")))
> "Face for highlighting failed part in Isearch echo-area message."
> + :version "23.1"
> :group 'isearch)
next prev parent reply other threads:[~2008-02-23 21:27 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 [this message]
2008-02-23 21:55 ` Juri Linkov
2008-02-23 23:12 ` Drew Adams
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='003001c87662$f62a0280$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).