[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Redshank gets loaded when exporting ELisp code blocks to HTML!?
From: |
Sebastien Vauban |
Subject: |
Re: [O] Redshank gets loaded when exporting ELisp code blocks to HTML!? |
Date: |
Fri, 02 May 2014 15:10:30 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.90 (windows-nt) |
Hello Sacha and Nicolas,
Answering after a (too) long time with very intermittent Internet
access...
Sacha Chua wrote:
> Sebastien Vauban writes:
>
>> Why are Emacs Lisp minor modes loaded for exporting the Org document
>> to HTML? If not necessary, this seems suboptimal (performance-wise).
>
> org-export-format-source-code-or-example loads the mode associated
> with the language in org-src-lang-modes in order to fontify the
> block.
Only to fontify, not to indent, right?
> You could check if org-export-current-backend is nil before
> loading anything that you want to use only interactively.
>
> Maybe like so?
>
> (add-hook 'emacs-lisp-mode-hook (lambda ()
> (unless org-export-current-backend
> (turn-on-redshank-mode))))
This seems to be a solution (although I did not test it), but it seems
as well impractical: I'd have to chase almost all minor modes of all
languages...
Can't we assume that the major modes have all the information to fontify
the code blocks, and -- if yes -- have a manner to forbid loading all
the minor modes at once (as, then, they'd be completely useless for the
export process)?
Best regards,
Seb
--
Sebastien Vauban
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [O] Redshank gets loaded when exporting ELisp code blocks to HTML!?,
Sebastien Vauban <=