unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 8679@debbugs.gnu.org, larsi@gnus.org
Subject: bug#8679: 24.0.50; wrong isearch highlighting for mismatch
Date: Tue, 11 Feb 2014 08:58:12 -0800 (PST)	[thread overview]
Message-ID: <1558a896-e67e-4c05-b87e-82ccd45bfbdd@default> (raw)
In-Reply-To: <<837g91ty7t.fsf@gnu.org>>

> Why is that a bug?  What do you get with this simplified recipe?
> 
>   emacs -Q
>   C-s eZZZZ
> 
> When you type 'e', all the 'e's in the buffer are highlighted, but
> the 'e' in the echo area is highlighted in pink.

It depends where you start the search.  If you start with point
at eob then what you say is true.

If you start the search at bob then the `e' is not pink when you
just type `e'.  When you then type `ZZZZ', so your search string is
now `eZZZZ', the buffer highlighting disappears (there are no
matches).

The mismatched portion of your search string, which is the `ZZZZ'
portion, is highlighted pink, to show that it is a mismatch.
This is the correct (intended) behavior.

> As soon as you type the first 'Z', the highlight in the buffer goes
> away, and the whole "eZ" in the echo area is colored in pink.

See above.

> And that is what I would expect.

It might be all we can reasonably expect; I don't know.  Probably
Juri can answer that.  And yes, in that case this is probably
also the answer to the bug fix request: it might not be easy to
fix.

But the intended behavior of the pink highlighting is to highlight
the mismatch portion of the search string.  What this means is that
there is a bug - the intention is not to highlight also the matched
portion.  It may not be a bug that we can fix, but it is a bug.

> What you seem to expect happens when the search wraps around, but no
> such wrap-around happens in your recipe.






       reply	other threads:[~2014-02-11 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<066C4D0D5E9344B6AA56A2F57400BE27@us.oracle.com>
     [not found] ` <<87r47c7plr.fsf@building.gnus.org>
     [not found]   ` <<715a78fd-35fb-41de-b523-5f86484a0369@default>
     [not found]     ` <<837g91ty7t.fsf@gnu.org>
2014-02-11 16:58       ` Drew Adams [this message]
2014-02-11 20:11         ` bug#8679: 24.0.50; wrong isearch highlighting for mismatch Juri Linkov
2011-05-16 20:36 Drew Adams
2011-05-16 21:57 ` Juri Linkov
2011-05-16 22:13   ` Drew Adams
2014-02-09  6:43 ` Lars Ingebrigtsen
2014-02-11 15:23   ` Drew Adams
2014-02-11 16:23     ` 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=1558a896-e67e-4c05-b87e-82ccd45bfbdd@default \
    --to=drew.adams@oracle.com \
    --cc=8679@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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).