Re: lax matching is not a great default behavior

[Artur Malabarba]

2015-12-02 3:37 GMT+00:00 Eli Zaretskii <address@hidden>:
>> Date: Tue, 1 Dec 2015 23:31:18 +0000
>> From: Artur Malabarba <address@hidden>
>> Cc: Mark Oteiza <address@hidden>, emacs-devel <address@hidden>
>>
>> > Seems to be lazy-highlight.  Set isearch-lazy-highlight to nil, and
>> > Bob's your uncle.
>>
>> If lazy-highlighting adds a lag before the user can move to the second
>> match, then we need to fix lazy-highlighting to not block input.
>
> Yes, but do you understand why it's a problem anyway?  Lazy hilighting
> uses the same regexp search functions and the same regexp as the code
> that find the first hit.  We are talking about 2 cases where there's
> no other matches for that regexp.  So how come finding out that there
> are no more matches is almost instantaneous, but looking for them as
> part of lazy-highlighting is so slow?

Yes. lazy-highlight is definitely doing something wrong. If I can hit
C-s and instantly be told "no more matches", lazy-highlight shouldn't
be slow at all.
I just tested here and the same happens for me.