unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 14:08:11 +0300	[thread overview]
Message-ID: <838s47kov8.fsf@gnu.org> (raw)
In-Reply-To: <87eedzujpv.fsf@gmail.com> (message from Augusto Stoffel on Sat,  22 May 2021 12:49:16 +0200)

> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 48581@debbugs.gnu.org
> Date: Sat, 22 May 2021 12:49:16 +0200
> 
> > You assume that (a) the main purpose of Isearch is to count the
> > matches,
> 
> No, the main purpose of Isearch is to search for a string :-).
> `isearch-lazy-highlight-buffer-update' has more than one purpose, but I
> assume that finishing faster is always better than taking longer than
> necessary.

In most real-life cases, at least in mine, you never need to look at
all the matches, only at the first few.

> However, the delay before the lazy count appears in the echo area during
> day-to-day Isearch operation is noticeable to the naked eye.  If you
> keep looking, you will notice it.

I know it's noticeable, and that directly contradicts your time
estimations, because human eyes cannot notice such short delays.  In
general, anything shorter than 50 ms will look instantaneous to us, at
least IME.





  reply	other threads:[~2021-05-22 11:08 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 [this message]
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
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=838s47kov8.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).