From: Eric S Fraga <firstname.lastname@example.org>
To: Emacs Org mode mailing list <email@example.com>
Subject: flyspell overlays removed in comments: does this make sense?
Date: Mon, 20 Dec 2021 16:56:38 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
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 , I ended
up looking at the code, specifically
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
Or have I misunderstood something fundamental?
 The unrelated reason is that I was looking at how I could get my own
user-defined meta lines ("#+calc: " for my use of embedded calc in org,
for the curious amongst you) fontified the way I want them. Not easy,
as far as I can see. I further noticed that org also removes flyspell
overlays from any "other" meta line, i.e. any other meta line not
processed by specific code.
: Eric S Fraga, with org release_9.5.1-279-g8908fb in Emacs 29.0.50
: Latest paper written in org: https://arxiv.org/abs/2106.05096
next reply other threads:[~2021-12-20 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:56 Eric S Fraga [this message]
2021-12-22 14:10 ` flyspell overlays removed in comments: does this make sense? Ihor Radchenko
2021-12-28 15:01 ` Eric S Fraga
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).