emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [org-babel] switching off (re-)evaluation of code blocks during Org export
Date: Tue, 22 Nov 2011 10:46:48 +0100	[thread overview]
Message-ID: <8062ictrp3.fsf@somewhere.org> (raw)
In-Reply-To: 87aa7plzl8.fsf@gmail.com

Hi Eric,

Eric Schulte wrote:
> Torsten Anders <torsten.anders-nRKTKYnHphK1Qrn1Bg8BZw@public.gmane.org> writes:
>> Thanks a lot for your kind replies. However, this is not yet quite what I am after.
>>
>> I want to be able to manually execute each code block, but not
>> automatically whenever the whole document is rendered. So, I would
>> always switch on/off "eval never". Hm...
>
> I've just pushed up a patch which adds a new option to the "eval" header
> argument. Setting eval to "non-export" will now allow interactive
> evaluation, but will inhibit code block evaluation during export. This
> should address your need as I understand it.

It certainly is a good addition, but wouldn't it be better to add an
orthogonal argument for the "exports" stuff, that is a second parameter?

I mean: you've added `non-export' which maps to:

- `yes' for interactive evaluation
- `never' for export

I'm sure a guy (or a woman) will ask in a short future for:

- `query' for interactive evaluation
- `never' for export.

Hence, maybe we should be able to set 2 possible behaviors[1] for the `eval'
parameter:

- one for the interactive mode (yes/query/no), and
- one for the export mode (yes/no, and maybe query as well?).

Best regards,
  Seb

Footnotes:

[1] Like for results, where we can give up to 3 options:
    `:results output scalar raw'

-- 
Sebastien Vauban

  reply	other threads:[~2011-11-22  9:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  0:13 [org-babel] switching off (re-)evaluation of code blocks during Org export Torsten Anders
2011-11-22  1:23 ` Eric Schulte
2011-11-22  9:46   ` Sebastien Vauban [this message]
2011-11-22 14:02     ` Eric Schulte
2011-11-22 17:15       ` Bernt Hansen
2011-11-22 17:31         ` Eric Schulte
2011-11-27 20:12   ` Torsten Anders
2011-11-28  7:13     ` Eric Schulte
2011-11-28 10:01       ` Torsten Anders
  -- strict thread matches above, loose matches on Subject: below --
2011-11-21 16:37 Torsten Anders
2011-11-21 17:26 ` Sebastien Vauban
2011-11-21 17:34   ` Eric Schulte

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=8062ictrp3.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /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).