Re: lax matching is not a great default behavior

[martin rudalics]

>> 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?

I'd blame the overlay mechanism.

martin