Re: lazy-count-update-hook run with inconsistent point

[Juri Linkov <juri@linkov.net>]

>> What do you think about lazy-count-update-hook being run with
>> inconsistent point? It's called from three points in isearch.el and from
>> best I can tell, for two of those (in isearch-lazy-highlight-new-loop)
>> it is always called with point at the current match (start or end
>> depending on forward or reverse search); however the last call (in
>> isearch-lazy-highlight-buffer-update) is inside the save-excursion and
>> so the point is wherever the last overlay has been created.
> ...
> Anyway, that was an oversight.  Does the patch below solve the problem?
> ...
> @@ -4342,11 +4342,12 @@ isearch-lazy-highlight-buffer-update
>  		  (setq isearch-lazy-count-current
>  			(gethash opoint isearch-lazy-count-hash 0))
>                    (when (and isearch-mode (null isearch-message-function))
> -                    (isearch-message))
> -		  (run-hooks 'lazy-count-update-hook))
> +                    (isearch-message)))
>  	      (setq isearch-lazy-highlight-timer
>  		    (run-at-time lazy-highlight-interval nil
> -				 'isearch-lazy-highlight-buffer-update)))))))))
> +				 'isearch-lazy-highlight-buffer-update)))))
> +        (when nomore
> +          (run-hooks 'lazy-count-update-hook))))))

Running the hook was also under another condition:
`(when isearch-lazy-count ...)'.  Shouldn't it be added
to `(when nomore ...)' too?