From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Unconditionally turn off Flyspell mode during export
Date: Wed, 26 Mar 2014 16:16:20 +0100 [thread overview]
Message-ID: <86siq5ng6z.fsf@somewhere.org> (raw)
In-Reply-To: 87wqfii6xf.fsf@bzg.ath.cx
Hi Bastien,
Bastien wrote:
> Sebastien Vauban writes:
>>
>> (add-hook 'text-mode-hook
>> (lambda ()
>> (message "Turning on Flyspell in buffer `%s'" (buffer-name))
>> (flyspell-mode 1)))
>>
>> 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:
>
> From master, you can check against `org-babel-exp-reference-buffer' to
> see if you are currently exporting, and then activate flyspell-mode
> only if you're not.
IIUC, I can't make use of it. Let me explain...
As that variable is only defined in Org mode, I must make such a check
in `org-mode-hook' only (not anymore in `text-mode-hook'):
--8<---------------cut here---------------start------------->8---
(add-hook 'org-mode-hook
(lambda ()
(unless (and (boundp 'org-babel-exp-reference-buffer)
org-babel-exp-reference-buffer)
(message "Turning on Flyspell in buffer `%s'" (buffer-name))
(turn-on-flyspell))))
--8<---------------cut here---------------end--------------->8---
Hence, if I don't enable Flyspell anymore in Text mode, I don't have
Flyspelling for common text files (not in Org mode). Not what I want.
If I do enable Flyspell in Text mode, I'm back on square one: my problem
is not solved.
Am I missing something?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-03-26 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 16:07 Unconditionally turn off Flyspell mode during export Sebastien Vauban
2014-03-25 16:23 ` Bastien
2014-03-26 15:16 ` Sebastien Vauban [this message]
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=86siq5ng6z.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
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).