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 16:35:22 +0300 [thread overview]
Message-ID: <83v97aki1x.fsf@gnu.org> (raw)
In-Reply-To: <87k0nqsyfr.fsf@gmail.com> (message from Augusto Stoffel on Sat, 22 May 2021 15:14:16 +0200)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 48581@debbugs.gnu.org
> Date: Sat, 22 May 2021 15:14:16 +0200
>
> On Sat, 22 May 2021 at 15:30, Eli Zaretskii <eliz@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.
next prev parent reply other threads:[~2021-05-22 13:35 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
2021-05-22 13:14 ` Augusto Stoffel
2021-05-22 13:35 ` Eli Zaretskii [this message]
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=83v97aki1x.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).