unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: Patch to avoid flicker in Isearch with lazy count
Date: Thu, 28 Jan 2021 12:17:06 +0100	[thread overview]
Message-ID: <87lfcd5n0t.fsf@gmail.com> (raw)
In-Reply-To: <871re5e809.fsf@mail.linkov.net> (Juri Linkov's message of "Thu,  28 Jan 2021 11:06:38 +0200")

On Thu, 28 Jan 2021 at 11:06, Juri Linkov <juri@linkov.net> wrote:

> Definitely, ‘lazy-highlight-delay-max-chars’ should not affect
> ‘lazy-highlight-interval’ because with pauses between highlighting
> portions of matches, when lazy-highlight-buffer-max-at-a-time is 20,
> this could create a situation when only first 20 matches are counted,
> and during the delay before processing the next portion of matches,
> the users might think this is the final total of all existing matches,
> so this is misleading for users.

Good, I'll make it so.  By the way, why is the default
‘lazy-highlight-buffer-max-at-a-time’ (20) so low?  The overhead of
creating a timer for every 20 matches is pretty substantial.  On my
machine, a value like 500 or 1000 makes the lazy count finish visibly
faster, and doesn't affect responsiveness even in huge files.



  reply	other threads:[~2021-01-28 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 15:41 Patch to avoid flicker in Isearch with lazy count Augusto Stoffel
2021-01-27 17:48 ` Juri Linkov
2021-01-28  7:32   ` Augusto Stoffel
2021-01-28  9:06     ` Juri Linkov
2021-01-28 11:17       ` Augusto Stoffel [this message]
2021-01-28 18:48         ` Juri Linkov
2021-01-29 17:50       ` Augusto Stoffel
2021-01-30 18:50         ` Juri Linkov
2021-09-04 22:43           ` Stefan Kangas
2021-09-05  7:54             ` 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=87lfcd5n0t.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).