From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 8679@debbugs.gnu.org
Subject: bug#8679: 24.0.50; wrong isearch highlighting for mismatch
Date: Mon, 16 May 2011 15:13:16 -0700 [thread overview]
Message-ID: <EE9DEDE4393D45E7912F0C825C688931@us.oracle.com> (raw)
In-Reply-To: <874o4u48dg.fsf@mail.jurta.org>
> > Not sure there is an easy fix for this one. And it's not very
> > important. But worth logging for future reference, at least.
>
> Currently it has exactly the same behavior as you asked in
> http://thread.gmane.org/gmane.emacs.devel/74539/focus=74614
Not as I _asked_, but as I _stated_ was probably "as good as it gets". To which
I added, "but I'm open, if someone has a better idea". I said "I don't know how
to fix that."
Actually, I forgot about that bug thread. ;-)
This time I'm saying something similar, but the use case is different. What I
said before is still true, but this report is about the behavior after `M-e', so
the consideration about a buffer change doesn't really apply.
IOW, both observations are relevant, I think. For this use case (same buffer
where `M-e' was used), it might be good if after editing the matching part were
not highlighted as a mismatch. Again, dunno whether that would be an easy fix -
I doubt it, but maybe you have an idea.
I have no good idea about this. Do you?
next prev parent reply other threads:[~2011-05-16 22:13 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 [this message]
2014-02-09 6:43 ` Lars Ingebrigtsen
2014-02-11 15:23 ` Drew Adams
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=EE9DEDE4393D45E7912F0C825C688931@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8679@debbugs.gnu.org \
--cc=juri@jurta.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.