Eric S Fraga <e.fr...@ucl.ac.uk> writes: > for some time (years, really), I've suffered with flyspell overlays > disappearing in comments in org documents. It never occurred to me that > this was due to org itself so I just put up with and chalked it up to > one of those Emacs mysteries. Today, for unrelated reasons [1], I ended > up looking at the code, specifically
Not only comments. Same for #+captions (which made me miss spelling errors in my figure captions). > org-fontify-meta-lines-and-blocks-1 > > and see that org explicitly removes flyspell overlays in comments. > > Before I look into maybe adding a user option for the flyspell issue, > can somebody explain the rationale for this? My comments tend to be > natural languages so flyspell is most definitely useful. Okay, spelling > errors in comments may matter less in terms of dissemination but > still... Looking at git log, the intention was avoiding flyspell highlights in cases like #+IKNOWTHISISNOTREALWORD: keyword value. Removing the highlights from user text is a side effect. I consider this a bug and mark your report as such. Confirmed Best, Ihor
