From: Juri Linkov <juri@jurta.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14729@debbugs.gnu.org, Dani Moncayo <dmoncayo@gmail.com>
Subject: bug#14729: 24.3.50; Isearch oddity
Date: Sat, 04 Dec 2021 21:59:16 +0200 [thread overview]
Message-ID: <865ys4taxv.fsf@mail.linkov.net> (raw)
In-Reply-To: <87h7bpqb6q.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 04 Dec 2021 04:51:57 +0100")
>> `isearch-fail-pos' assumes that in a failed state of search
>> a shorter previous successful search string should be taken
>> as a basis for highlighting. In this case, the last successful match
>> was "buf", so an appended suffix is highlighted as failed.
>
> So, first we have:
>
>
>
>
> Then we type "fer", and then get:
>
>
>
>
> But... I think I'd expect getting
>
>
>
>
> instead? Probably.
Or to turn the failing search into a successful one
since the search string matches the buffer.
OTOH, the current behavior also makes sense
since it highlights the last failing characters
typed by the user. E.g. compare it with `C-s bufzzz'.
next prev parent reply other threads:[~2021-12-04 19:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 9:58 bug#14729: 24.3.50; Isearch oddity Dani Moncayo
2013-06-27 23:44 ` Juri Linkov
2013-06-29 17:22 ` Dani Moncayo
2013-06-29 21:53 ` Juri Linkov
2013-06-29 22:34 ` Dani Moncayo
2013-06-30 3:11 ` Drew Adams
2021-12-04 3:51 ` Lars Ingebrigtsen
2021-12-04 16:48 ` bug#14729: [External] : " Drew Adams
2021-12-04 19:59 ` Juri Linkov [this message]
2021-12-04 22:06 ` Lars Ingebrigtsen
2021-12-05 9:35 ` Juri Linkov
2021-12-05 20:22 ` Lars Ingebrigtsen
2021-12-06 2:09 ` bug#14729: [External] : " Drew Adams
2021-12-06 9:33 ` Juri Linkov
2021-12-06 9:40 ` Lars Ingebrigtsen
2021-12-06 16:01 ` Drew Adams
2021-12-06 17:03 ` Juri Linkov
2021-12-07 20:48 ` Lars Ingebrigtsen
2021-12-07 21:53 ` 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
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=865ys4taxv.fsf@mail.linkov.net \
--to=juri@jurta.org \
--cc=14729@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--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).