By default, the results of running M-x ispell-buffer
in org-mode are
very disappointing.
Ispell looks inside
:PROPERTY:
drawers, which commonly contain things like:ID: 797495bd-581b-4a42-883b-c2a55a08f08a
It tries to correct org statements! For instance, it complains about the
SRC
in#+BEGIN_SRC emacs-lisp
It goes inside org-blocks. I suppose this might be useful for blocks like
#+BEGIN_QUOTE
, but in source code blocks that’s just silly.
Is there a package that fixes all this?
I’d love to spell-check my writing but the amount of false-positives I’m getting makes it unfeasible.
If it matters, the OS's spell checker is aspell.
(get 'org-mode 'flyspell-mode-predicate)
), but I'm not sure how that could be generalised forispell-buffer
. – legoscia Sep 29 '14 at 13:03ispell-parser
, so flyspell's predicate might work well there with a wrapper around it. – Malabarba Sep 29 '14 at 13:11#+
or in source code blocks is not spell-checked. But normal text under headings is checked. I have these in my flyspell setup:(add-hook 'prog-mode-hook 'flyspell-prog-mode)
,(add-hook 'org-mode-hook 'turn-on-flyspell)
– Kaushal Modi Sep 29 '14 at 13:40ispell-parser
appears to be just a symbol, and code all over the place checks it for particular values. So nothing really extensible. – Sigma Sep 29 '14 at 21:48flyspell-lazy
package in addition toflyspell
which relegates spell-checking to idle periods. I've found this significantly speeded up Org-mode file editing with flyspell on (I got some unacceptable pauses before using this package). You have to tolerate spelling errors not appearing immediately, but I've not found that a significant problem. – Stuart Hickinbottom Oct 09 '14 at 07:34Can I prevent ispell from checking source blocks?
in http://orgmode.org/worg/org-faq.html ? – rvf0068 Oct 10 '14 at 01:55