GNU bug report logs - #48581
27.2; Default value of lazy-highlight-buffer-max-at-a-time is too low

Previous Next

Full log

Message #20 received at 48581 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Augusto Stoffel <arstoffel <at> gmail.com>
Cc: 48581 <at> debbugs.gnu.org
Subject: Re: bug#48581: 27.2; Default value of
 lazy-highlight-buffer-max-at-a-time is too low
Date: Sat, 22 May 2021 15:30:58 +0300

> From: Augusto Stoffel <arstoffel <at> gmail.com>
> Cc: 48581 <at> debbugs.gnu.org
> Date: Sat, 22 May 2021 14:17:25 +0200
> 
> On Sat, 22 May 2021 at 14:08, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> > In most real-life cases, at least in mine, you never need to look at
> > all the matches, only at the first few.
> 
> That's right.  However, despite the name,
> `lazy-highlight-buffer-max-at-a-time' also influences the time needed to
> compute the number of matches in the buffer.  So, when you set
> `isearch-lazy-count' to t, those numbers in the table of my first
> message indicate the delay between typing a search string and seeing the
> number of matches in the buffer (as well as the relative position of the
> current match) in the echo area.

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.