GNU bug report logs -
#48581
27.2; Default value of lazy-highlight-buffer-max-at-a-time is too low
Previous Next
Reported by: Augusto Stoffel <arstoffel <at> gmail.com>
Date: Sat, 22 May 2021 09:26:03 UTC
Severity: minor
Tags: fixed
Found in version 27.2
Fixed in version 28.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Augusto Stoffel <arstoffel <at> gmail.com>
> Cc: 48581 <at> debbugs.gnu.org
> Date: Sat, 22 May 2021 15:14:16 +0200
>
> On Sat, 22 May 2021 at 15:30, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> > That was exactly my point: the variable you suggest changing affects
> > more than just one use case, and it affects them in ways that in a
> > sense contradict one another.
> >
> > If we want to change the default value, we should find a way of doing
> > that without hurting "the other" use case.
>
> What are the other uses cases, and in which way could they be hurt by
> `isearch-lazy-highlight-buffer-update' being faster to finish?
The most obvious case is to find the first match and act on that.
Highlighting too many other matches will delay the response to the
next command.
This bug report was last modified 3 years and 357 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.