You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
Is there a possibility of an option to limit CPU use?
On a 2014 Macbook pro when I use vale with the vscode extension, vale briefly spikes to above 200% fan use while I type, which turns on the noisy fan and makes visual updates (markdown preview etc) lag a bit.
I wonder if there could be an option to limit the CPU usage of vale?
I have very very many rules, which I'm reluctant to trim, because apart from the fan noise, I find these many rules a net benefit.
Another idea (on the vscode extension side) would be to "debounce" so that rather than running immediately on each key-press, vale is fired only after a pause of say 5-10 seconds? Again this could be configurable?
Finally, again on the vscode extension side, I suspect vscode is sending the entire file to vale on each key press? Would it be realistic to send only the part (paragraph?) that has changed. I've notice the CPU/noise problem becomes much worse, the longer the document?
The text was updated successfully, but these errors were encountered:
OK, do you really suggest I create an issue there, too? Seems a bit messy to create two? I was under the impression errata-ai was quite a small organisation?
Finally, again on the vscode extension side, I suspect vscode is sending the entire file to vale on each key press? Would it be realistic to send only the part (paragraph?) that has changed. I've notice the CPU/noise problem becomes much worse, the longer the document?
Is there a possibility of an option to limit CPU use?
On a 2014 Macbook pro when I use vale with the vscode extension, vale briefly spikes to above 200% fan use while I type, which turns on the noisy fan and makes visual updates (markdown preview etc) lag a bit.
I wonder if there could be an option to limit the CPU usage of vale?
I have very very many rules, which I'm reluctant to trim, because apart from the fan noise, I find these many rules a net benefit.
Another idea (on the vscode extension side) would be to "debounce" so that rather than running immediately on each key-press, vale is fired only after a pause of say 5-10 seconds? Again this could be configurable?
Finally, again on the vscode extension side, I suspect vscode is sending the entire file to vale on each key press? Would it be realistic to send only the part (paragraph?) that has changed. I've notice the CPU/noise problem becomes much worse, the longer the document?
The text was updated successfully, but these errors were encountered: