From: Ihor Radchenko <firstname.lastname@example.org>
To: Eric S Fraga <email@example.com>
Cc: Emacs Org mode mailing list <firstname.lastname@example.org>
Subject: Re: flyspell overlays removed in comments: does this make sense?
Date: Wed, 22 Dec 2021 22:10:04 +0800 [thread overview]
Message-ID: <878rwcu3wj.fsf@localhost> (raw)
Eric S Fraga <email@example.com> 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 , I ended
> up looking at the code, specifically
Not only comments. Same for #+captions (which made me miss spelling
errors in my figure captions).
> 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
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.
next prev parent reply other threads:[~2021-12-22 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:56 flyspell overlays removed in comments: does this make sense? Eric S Fraga
2021-12-22 14:10 ` Ihor Radchenko [this message]
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).