Unconditionally turn off Flyspell mode during export

Unconditionally turn off Flyspell mode during export

[Sebastien Vauban]

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

Re: Unconditionally turn off Flyspell mode during export

[Bastien]

Hi Sébastien,

Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:

> I do that with:
>
>     (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.

HTH,

-- 
 Bastien

Re: Unconditionally turn off Flyspell mode during export

[Sebastien Vauban]

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

Re: Unconditionally turn off Flyspell mode during export

[Nick Dokos]

Sebastien Vauban <sva-news@mygooglest.com>
writes:

> 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:
>
>     (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:
>
> 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*, as it's completely useless (the export buffers are killed when
> the export is done) and eats useful CPU cycles?
>

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?

Untested.
-- 
Nick

Re: Unconditionally turn off Flyspell mode during export

[Sebastien Vauban]

Hello Nick and Bastien,

Nick Dokos wrote:
> Sebastien Vauban writes:
>>
>> 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.
>>
>> 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:
>>
>> 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*, as it's completely useless (the export buffers are killed when
>> the export is done) and eats useful CPU cycles?
>
> 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?

The code:

--8<---------------cut here---------------start------------->8---
  (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))
--8<---------------cut here---------------end--------------->8---

> Untested.

Better...

--8<---------------cut here---------------start------------->8---
Turning on Flyspell in buffer `ecm.txt'
Turning on Flyspell in buffer `ecm.html'
--8<---------------cut here---------------end--------------->8---

Still, the HTML [1] exported file is entirely Flyspell'ed...

Best regards,
  Seb

[1] HTML mode derives from Text mode.

-- 
Sebastien Vauban

Re: 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

Re: Unconditionally turn off Flyspell mode during export

[Bastien]

Hi Sébastien,

Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:

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

The only thing that comes to my mind right now is to disable
flyspell-mode through a hook in `org-export-before-processing-hook'.

I didn't test this though.

-- 
 Bastien