From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 48581@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <8335ufkl19.fsf@gnu.org> (raw)
In-Reply-To: <87k0nrklnu.fsf@gmail.com> (message from Augusto Stoffel on Sat, 22 May 2021 14:17:25 +0200)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 48581@debbugs.gnu.org
> Date: Sat, 22 May 2021 14:17:25 +0200
>
> On Sat, 22 May 2021 at 14:08, Eli Zaretskii <eliz@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.
next prev parent reply other threads:[~2021-05-22 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 9:25 bug#48581: 27.2; Default value of lazy-highlight-buffer-max-at-a-time is too low Augusto Stoffel
2021-05-22 9:44 ` Eli Zaretskii
2021-05-22 10:49 ` Augusto Stoffel
2021-05-22 11:08 ` Eli Zaretskii
2021-05-22 12:17 ` Augusto Stoffel
2021-05-22 12:30 ` Eli Zaretskii [this message]
2021-05-22 13:14 ` Augusto Stoffel
2021-05-22 13:35 ` Eli Zaretskii
2021-05-25 20:29 ` Juri Linkov
2021-05-31 20:33 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8335ufkl19.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48581@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).