From: Eli Zaretskii <eliz@gnu.org>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: nospam-abuse@ilyaz.org, emacs-devel@gnu.org
Subject: Re: [PATCH] 5x speedup of flyspell-buffer
Date: Fri, 14 Apr 2023 09:54:37 +0300 [thread overview]
Message-ID: <83wn2feyxe.fsf@gnu.org> (raw)
In-Reply-To: <87ildzm0dz.fsf@web.de> (arne_bab@web.de)
> From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
> Cc: Ilya Zakharevich <nospam-abuse@ilyaz.org>, emacs-devel@gnu.org
> Date: Fri, 14 Apr 2023 08:39:10 +0200
>
> > OK, then N = 50 should do the same trick.
>
> Wouldn’t that then show too few messages for small buffers?
There's no sense of showing messages for jobs that finish so fast.
> I quite like the logarithmic message showing, because it ensures that
> the user is informed of progress while avoiding a constant spew of
> messages.
The need for informing the user about the progress only exists when
the operation takes long enough time.
> The only thing I worry about is that there may at some point be too few
> messages, so a maximum might be useful to ensure that there is some
> progress notification at least once every few seconds. Otherwise users
> could think that it stalled.
How much over-engineering are we willing to put into this nit?
next prev parent reply other threads:[~2023-04-14 6:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 13:50 [PATCH] 5x speedup of flyspell-buffer Ilya Zakharevich
2023-04-13 6:54 ` Eli Zaretskii
2023-04-13 10:23 ` Ilya Zakharevich
2023-04-13 10:32 ` Eli Zaretskii
2023-04-13 20:29 ` Ilya Zakharevich
2023-04-14 5:47 ` Eli Zaretskii
2023-04-14 6:39 ` Dr. Arne Babenhauserheide
2023-04-14 6:54 ` Eli Zaretskii [this message]
2023-04-15 1:51 ` interacting during (sit-for 0). Was: " Ilya Zakharevich
2023-04-15 2:01 ` Ilya Zakharevich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wn2feyxe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arne_bab@web.de \
--cc=emacs-devel@gnu.org \
--cc=nospam-abuse@ilyaz.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.