From: Augusto Stoffel <arstoffel@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Yuan Fu <casouri@gmail.com>,
61814@debbugs.gnu.org, eliz@gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell
Date: Wed, 08 Mar 2023 09:50:14 +0100 [thread overview]
Message-ID: <87wn3r6309.fsf@gmail.com> (raw)
In-Reply-To: <86ttywwh9s.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 07 Mar 2023 20:25:19 +0200")
On Tue, 7 Mar 2023 at 20:25, Juri Linkov wrote:
>> I wonder if it’s possible or desirable to follow the flyspell’s behavior
>> but make it async? Preferably when some mechanism to discard unnecessary
>> spell checks. For example, I modified my scrolling functions to inhibit
>> flyspell from running in post-command-hook, which speeds up scrolling
>> considerably. Otherwise flyspell would try to spell check every word you
>> scrolled by and cause perceivable slow-down.
>
> There is a patch proposed recently in bug#61874 that does this.
Two administrative questions:
- Can/should I as the initiator of this ticket close it, given that it's
resolved?
- Is the use of this list to discuss bugs in ELPA packages encouraged or
rather not?
next prev parent reply other threads:[~2023-03-08 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 14:56 bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell Augusto Stoffel
2023-02-26 15:11 ` Eli Zaretskii
2023-02-26 15:36 ` Augusto Stoffel
2023-02-26 15:45 ` Eli Zaretskii
2023-02-27 8:31 ` Yuan Fu
2023-02-27 9:58 ` Augusto Stoffel
2023-03-04 11:41 ` Augusto Stoffel
2023-03-04 22:59 ` Yuan Fu
2023-03-06 10:52 ` Augusto Stoffel
2023-03-06 12:15 ` Eli Zaretskii
2023-03-08 0:45 ` Yuan Fu
2023-03-07 18:25 ` Juri Linkov
2023-03-08 8:50 ` Augusto Stoffel [this message]
2023-03-08 13:57 ` 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=87wn3r6309.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=61814@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
/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).