Closed ericsfraga closed 1 year ago
Thanks. This is a known issue - the Org-mode flyspell predicate can be slow under certain circumstances. My recommendation is that you remove jinx--flyspell-ignored-p
from the jinx--predicates
list. There is probably nothing we can do about this issue in Jinx. Maybe the Org maintainers could try to speed up the flyspell-mode-predicate
somehow. I would appreciate if you report the issue on the Org mailing list.
Okay, thank you. I didn't see this in the closed issues but maybe I didn't look close enough. I have reported this on the org mailing list.
Nothing wrong with reporting this! I meant that I have observed myself that the Org predicate is the most expensive step during checking. Another alternative which could work for you is to add a custom predicate early in the list such that the problematic block are skipped immediately before checking the words and before calling the flyspell predicate. But that's all we can do, either remove the flyspell predicate completely or prevent it from running by guarding it with an additional predicate.
See the mailing list thread: https://lists.gnu.org/archive/html/emacs-orgmode/2023-04/msg00092.html
I've been using jinx for some days now and really like it. It works very well generally. However, I've run into a strange case where jinx gets bogged down by org parsing. The file I have has several thousand lines that look like this:
Visiting the org file with jinx-mode enabled, Emacs basically freezes for some time with 100% CPU usage. The profile output for cpu usage shows:
with the memory usage
I will post a link to this issue on the org mailing list as well. Turning off jinx-mode restores normal behaviour in the org buffer.