From: Ihor Radchenko <yantar92@posteo.net>
To: Morgan Willcock <morgan@ice9.digital>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode-flyspell-verify: Why skip checking the LOGBOOK?
Date: Sat, 10 Aug 2024 15:02:16 +0000 [thread overview]
Message-ID: <87v808775z.fsf@localhost> (raw)
In-Reply-To: <87jzgpvdbk.fsf@ice9.digital>
Morgan Willcock <morgan@ice9.digital> writes:
> With org-log-into-drawer set to t any notes that are taken with
> org-add-note go into a LOGBOOK drawer, but this also removes the
> spell-checking provided by Flyspell.
>
> It seems intentional to prevent checking the LOGBOOK (or equivalent)
> when the value of org-log-into-drawer is non-nil:
>
> ;; Ignore checks in LOGBOOK (or equivalent) drawer.
> ((let ((log (org-log-into-drawer)))
> (and log
> (let ((drawer (org-element-lineage element 'drawer)))
> (and drawer
> (org-string-equal-ignore-case
> log (org-element-property :drawer-name drawer))))))
> nil)
>
> ...but why should the location of the note matter to the spell-checker?
I am not sure about the reasoning behind disabling flyspell inside
logbook drawers. I cannot find anything meaningful in git history either.
> Is there any way to re-enable spell-checking of the notes without adding
> advice to org-mode-flyspell-verify to hijack the result?
It looks like LOGBOOK drawers should not be ignored by flyspell.
May you comment out that check locally and see how it goes?
Ideally, please check things like CLOCK and automatic todo state change
notes.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-08-10 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 17:03 org-mode-flyspell-verify: Why skip checking the LOGBOOK? Morgan Willcock
2024-08-10 15:02 ` Ihor Radchenko [this message]
2024-08-10 17:19 ` Morgan Willcock
2024-08-11 15:33 ` Ihor Radchenko
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v808775z.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=morgan@ice9.digital \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).