emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Simon Thum <simon.thum@gmx.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>, OSiUX <xuiso@osiux.com.ar>
Cc: emacs-orgmode@gnu.org
Subject: Re: export ICal without evaluate code block
Date: Wed, 26 Feb 2014 21:00:14 +0100	[thread overview]
Message-ID: <530E47CE.9020209@gmx.de> (raw)
In-Reply-To: <87y50yrm97.fsf@gmail.com>

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 <xuiso@osiux.com.ar> 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,
>

  parent reply	other threads:[~2014-02-26 20:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 22:39 export ICal without evaluate code block OSiUX
2014-02-26 14:17 ` Nicolas Goaziou
2014-02-26 16:06   ` OSiUX
2014-02-26 16:46     ` Nicolas Goaziou
2014-02-26 19:25       ` OSiUX
2014-02-26 20:00   ` Simon Thum [this message]
2014-02-26 21:21     ` Nicolas Goaziou
2014-03-03 21:02       ` Simon Thum
2014-03-13 15:42         ` Bastien
2014-03-17 15:16           ` Simon Thum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530E47CE.9020209@gmx.de \
    --to=simon.thum@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=xuiso@osiux.com.ar \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).