emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: sebastien.miquel@posteo.eu
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-compat.el (org-mode-flyspell-verify): Do not spell check code in headline
Date: Sun, 14 Mar 2021 22:56:56 -0400	[thread overview]
Message-ID: <87sg4xi0p3.fsf@kyleam.com> (raw)
In-Reply-To: <8d13a201-8243-9c7a-93eb-48f1d7fb9ec5@posteo.eu>

Sébastien Miquel writes:

> Subject: [PATCH] org-compat.el (org-mode-flyspell-verify): Do not check code
>  in headline
> * lisp/org-compat.el (org-mode-flyspell-verify): Do not spell check
> code, verbatim and LaTeX fragments in headline title.

Makes sense.  Hopefully the cost of the org-element-at-point call isn't
too noticeable.

Applied to master (7c4d057cd), adding a TINYCHANGE cookie to the commit
message.  You're bumping up against the cumulative number of changes
allowed without assigning copyright, so please consider completing the
copyright paperwork (or, if you've already done so, please let me know
I'll update your status listed at


  reply	other threads:[~2021-03-15  2:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 16:27 [PATCH] org-compat.el (org-mode-flyspell-verify): Do not spell check code in headline Sébastien Miquel
2021-03-15  2:56 ` Kyle Meyer [this message]
2021-03-15  6:40   ` Sébastien Miquel

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:

  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=87sg4xi0p3.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastien.miquel@posteo.eu \


* 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).