[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[O] Redshank gets loaded when exporting ELisp code blocks to HTML!?

From: Sebastien Vauban
Subject: [O] Redshank gets loaded when exporting ELisp code blocks to HTML!?
Date: Mon, 07 Apr 2014 16:38:26 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (windows-nt)


Incidentally, because I had removed `paredit.el' from my load-path,
I could not export any Org file anymore which contained just one simple
`emacs-lisp' code block, such as:

--8<---------------cut here---------------start------------->8---


#+begin_src emacs-lisp
M-x load-library RET ox-beamer RET
--8<---------------cut here---------------end--------------->8---

I found the culprit lines being:

--8<---------------cut here---------------start------------->8---
  ;; Common Lisp editing extensions
  (autoload 'redshank-mode "redshank"
    "Minor mode for restructuring Lisp code (i.e., refactoring)." t)

  (add-hook 'emacs-lisp-mode-hook 'turn-on-redshank-mode)
--8<---------------cut here---------------end--------------->8---


- Redshank requires ParEdit, and
- ParEdit was not found anymore.

What I don't understand is:

    Why are Emacs Lisp minor modes loaded for exporting
    the Org document to HTML?

If not necessary, this seems suboptimal (performance-wise).

Is it really necessary?  I don't think so, because if I comment the
Redshank activation, then I can still export to HTML as before.  I just
loose the editing features in my real Emacs Lisp buffers.

So, is there a way to disactivate those minor modes during export?

Best regards,

Sebastien Vauban

reply via email to

[Prev in Thread] Current Thread [Next in Thread]