From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26525@debbugs.gnu.org
Subject: bug#26525: `sit-for' in Flyspell slows typing down, hogs 90% of CPU
Date: Mon, 17 Apr 2017 09:29:20 -0400 [thread overview]
Message-ID: <2c330c44-4919-7d2f-cb20-c9b72c9e8050@gmail.com> (raw)
In-Reply-To: <83r30recae.fsf@gnu.org>
On 2017-04-17 03:14, Eli Zaretskii wrote:
>> But the condition and the comment seem at odds, and it doesn't say much about why it calls `sit-for`.
>
> I'm not quite sure what needs to be explained. I think the doc string
> of flyspell-delay and flyspell-default-delayed-commands tell the whole
> story; if something is unclear there, please say what is unclear.
The code reads (cond ((get this-command 'flyspell-delayed) …)), but the comment says "The current command is not delayed". Does a non-nil flycheck-delayed really mean that the command is *not* delayed?
> If you want to see this feature in action, turn on Flyspell, then type
> something like "ssss", and then wait _without_ typing any non-word
> character. You will see that the mis-spelled word is marked only
> after 3 sec, the default value of flyspell-delay. Then contrast that
> with the same word with a space typed after it.
Thanks! I don't expect that this feature is intended to slow down typing, though, right? In the example I posted it makes typing painfully slow.
Clément.
next prev parent reply other threads:[~2017-04-17 13:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 20:28 bug#26525: `sit-for' in Flyspell slows typing down, hogs 90% of CPU Clément Pit-Claudel
2017-04-15 20:33 ` Clément Pit-Claudel
2017-04-17 7:14 ` Eli Zaretskii
2017-04-17 13:29 ` Clément Pit-Claudel [this message]
2017-04-17 14:25 ` Eli Zaretskii
2017-04-17 15:36 ` Clément Pit-Claudel
2020-08-13 1:41 ` Stefan Kangas
2017-10-17 12:07 ` Damien Cassou
2020-08-28 11:49 ` Stefan Kangas
2020-08-28 12:35 ` Damien Cassou
2020-08-28 18:40 ` Clément Pit-Claudel
2020-08-29 16:27 ` Stefan Kangas
2020-08-29 18:10 ` Clément Pit-Claudel
2020-09-02 23:15 ` Nick H
2020-09-03 10:19 ` Stefan Kangas
2020-09-04 1:01 ` Nick Helm
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=2c330c44-4919-7d2f-cb20-c9b72c9e8050@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=26525@debbugs.gnu.org \
--cc=eliz@gnu.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 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).