Re: [O] Unconditionally turn off Flyspell mode during export

[Sebastien Vauban]

Hello,

May I bump up this thread?

Sebastien Vauban wrote:
> Nick Dokos wrote:
>> Sebastien Vauban writes:
>>> I use Flyspell in all my text-mode, hence as well in my Org mode
>>> buffers -- as they ultimately derive from Text mode.
>>>
>>> That has the perverse impact that Flyspell gets called (even
>>> multiple times) during the export process, when creating copies of
>>> the source Org document:
>>>
>>> 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
>>>
>>> Is it possible to *automatically disable Flyspell during the export*
>>> *process*?
>>
>> Advise org-export-as with an `around' piece of advice where you set
>> the text-mode-hook to nil (or just delete the flyspell part) perhaps?
>
>   (add-hook 'text-mode-hook
>             (lambda ()
>               (message "Turning on Flyspell in buffer `%s'" (buffer-name))
>               (flyspell-mode 1)))
>
>   (defadvice org-export-as (around my-org-export-as activate)
>     "Turn off Flyspell (and other things) when exporting current Org buffer."
>     (let (text-mode-hook)
>       ad-do-it))
>
> Better... Still, the HTML [1] exported file is entirely Flyspell'ed...
>
> Turning on Flyspell in buffer `ecm.txt'
> Turning on Flyspell in buffer `ecm.html'
>
> [1] HTML mode derives from Text mode.

Is there an alternative way to stop Org from Flyspell'ing all the
(temporary) export files?

Best regards,
  Seb

-- 
Sebastien Vauban