all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 8679@debbugs.gnu.org
Subject: bug#8679: 24.0.50; wrong isearch highlighting for mismatch
Date: Tue, 11 Feb 2014 07:23:26 -0800 (PST)	[thread overview]
Message-ID: <715a78fd-35fb-41de-b523-5f86484a0369@default> (raw)
In-Reply-To: <87r47c7plr.fsf@building.gnus.org>

> > In this case the mismatch highlighting is inaccurate:
> >
> > emacs -Q
> > C-x b *scratch*
> > C-s ZZZZ
> >
> > The entire search string is highlighted as a mismatch, which is
> > correct.
> >
> > M-e M-a e
> >
> > So the edited search string is eZZZZ.
> >
> > C-s
> >
> > The entire search string, `eZZZZ' is highlighted, even though
> > there are matches for the `e'.
> 
> Seems to work for me.  Closing.

Seems to work for you apparently means little, I'm afraid.

Still a bug on Windows, at least.  The only difference in the
recipe now is that you need not use M-a.  The point is that
after inserting `e' at the front of the search string, `C-s'
still highlights the whole search string, `eZZZZ', instead of
highlighting only the mismatch portion, `ZZZZ'.

Should be reopened and fixed.





  reply	other threads:[~2014-02-11 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 20:36 bug#8679: 24.0.50; wrong isearch highlighting for mismatch 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 [this message]
2014-02-11 16:23     ` Eli Zaretskii
     [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
2014-02-11 20:11         ` Juri Linkov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=715a78fd-35fb-41de-b523-5f86484a0369@default \
    --to=drew.adams@oracle.com \
    --cc=8679@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.