[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#26525: `sit-for' in Flyspell slows typing down, hogs 90% of CPU
From: |
Clément Pit-Claudel |
Subject: |
bug#26525: `sit-for' in Flyspell slows typing down, hogs 90% of CPU |
Date: |
Mon, 17 Apr 2017 09:29:20 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
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.