emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Unconditionally turn off Flyspell mode during export
Date: Tue, 25 Mar 2014 17:07:58 +0100	[thread overview]
Message-ID: <86ha6mclcx.fsf@somewhere.org> (raw)

Hello,

I use Flyspell in all my text-mode and prog-mode buffers, hence as well
in my Org mode buffers -- as they ultimately derive from Text mode.

I do that with:

--8<---------------cut here---------------start------------->8---
    (add-hook 'text-mode-hook
              (lambda ()
                (message "Turning on Flyspell in buffer `%s'" (buffer-name))
                (flyspell-mode 1)))
--8<---------------cut here---------------end--------------->8---

Though, as you can see, that has the perverse impact that Flyspell gets
called (even multiple times) during the export process, when creating
copies of the source Org document:

--8<---------------cut here---------------start------------->8---
Turning on Flyspell in buffer `ecm.txt<2>'
Turning on Flyspell in buffer `ecm.txt<2><2>'
Turning on Flyspell in buffer ` *temp*'
Turning on Flyspell in buffer `ecm.html'
Saving file d:/ecm.html...
Wrote d:/ecm.html
--8<---------------cut here---------------end--------------->8---

Is it possible to *automatically disable Flyspell during the export*
*process*, as it's completely useless (the export buffers are killed when
the export is done) and eats useful CPU cycles?

Best regards,
  Seb

-- 
Sebastien Vauban

next             reply	other threads:[~2014-03-25 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 16:07 Sebastien Vauban [this message]
2014-03-25 16:23 ` Unconditionally turn off Flyspell mode during export Bastien
2014-03-26 15:16   ` Sebastien Vauban
2014-03-26 17:31 ` Nick Dokos
2014-03-28 10:41   ` Sebastien Vauban
2014-04-05  7:47     ` Sebastien Vauban
2014-04-11  9:03       ` Bastien

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=86ha6mclcx.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /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

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