From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: 74437@debbugs.gnu.org, mail@alternateved.com
Subject: bug#74437: 30.0.92; completion-preview-idle-delay is delayed by flyspell
Date: Tue, 19 Nov 2024 21:10:36 +0200 [thread overview]
Message-ID: <861pz7t4yb.fsf@gnu.org> (raw)
In-Reply-To: <m134jnf4oo.fsf@macbookpro.home> (message from Eshel Yaron on Tue, 19 Nov 2024 19:40:07 +0100)
> From: Eshel Yaron <me@eshelyaron.com>
> Cc: 74437@debbugs.gnu.org, mail@alternateved.com
> Date: Tue, 19 Nov 2024 19:40:07 +0100
>
> +(defcustom flyspell-blocking-delay t
I'd name this flyspell-use-timer or somesuch.
> + "Whether to block Emacs while Flyspell waits after a delayed command."
> + :type 'boolean
> + :version "30.1")
^^^^^^^^^^^^^^
You are an optimist ;-)
> - (accept-process-output ispell-process)
> + (accept-process-output ispell-process 1)
Does this really work reliably from a timer? You _are_ aware that
this call to accept-process-output will run timers while we wait?
Also, what happens if there are other async subprocesses running in
parallel, like maybe Grep or compilation or url-retrieve?
next prev parent reply other threads:[~2024-11-19 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 11:55 bug#74437: 30.0.92; completion-preview-idle-delay is delayed by flyspell Tomasz Hołubowicz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 16:13 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 16:56 ` Tomasz Hołubowicz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 17:19 ` Eli Zaretskii
2024-11-19 18:40 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 19:10 ` Eli Zaretskii [this message]
2024-11-19 20:16 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-20 13:04 ` Eli Zaretskii
2024-11-20 15:52 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-20 16:29 ` Eli Zaretskii
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=861pz7t4yb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74437@debbugs.gnu.org \
--cc=mail@alternateved.com \
--cc=me@eshelyaron.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).