|
From: | Simon Thum |
Subject: | Re: [O] export ICal without evaluate code block |
Date: | Wed, 26 Feb 2014 21:00:14 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 |
Nicolas,I recently had a similar problem, though in my case the iClaendar export wasn't even reached because emacs started asking in other exports that came before.
I have some worries here; Why is it so hard to avoid evaluation/modification in org files during export?
I use -batch, I would have tought that was enough, but if I'm getting your answer below right, then setting those 2 parameters is not enough either, because some backends fiddle with them?
I have searched the docs but did not find anything about backends overriding these settings.
Enlightenment is appreciated. Cheers, Simon On 02/26/2014 03:17 PM, Nicolas Goaziou wrote:
Hello, OSiUX <address@hidden> writes:Calendar can be exported without evaluating babel code blocks? I try setting in .emacs: (setq org-confirm-babel-evaluate nil) (setq org-export-babel-evaluate nil) but always evaluate when exports iCalendar :-(You could use something like this: (defun my-toggle-off-babel (backend) (when (org-export-derived-backend-p backend 'icalendar) (org-set-local 'org-confirm-babel-evaluate nil) (org-set-local 'org-export-babel-evaluate nil))) (add-hook org-export-before-processing-hook #'my-toggle-off-babel) Regards,
[Prev in Thread] | Current Thread | [Next in Thread] |