emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: [Bug] [babel] calls in :noexport: subtrees evaluated
Date: Wed, 05 Sep 2012 14:15:21 +0200	[thread overview]
Message-ID: <87oblkbr8m.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 80y5ko3cko.fsf@somewhere.org

Hi Sebastien,


"Sebastien Vauban"
<wxhgmqzgwmuf@spammotel.com> writes:

> Hello Andreas,
>
> Andreas Leha wrote:
>> it seems to me, that #+call lines in subtrees with the :noexport: tag
>> are evaluated.  Is this intended?
>
> I think that, at least, it's not a bug. I don't /think/ it has never been
> specified like that. But I still don't have a clear view of what is done, in
> which order:
>
> - processing macros
> - inhibiting "noexport" subtrees
> - evaluating code blocks (possibly with noweb calls)
> - etc.
>
> In fact, what you expect is that putting a tag ":noexport:" on a subtree would
> propagate the option ":eval no-export"[1] to all code blocks beneath it. That's
> the one which inhibits code block evaluation during export (but allow
> interactive evaluation).

Thanks for the pointer.  I am aware of that.  But this requires two
modifications, in order to get the desired behaviour: the :noexport: tag
and a 'eval no-export' property.

Just to
explain my use case.  I am doing a statistical analysis.  One "arm" in
that analysis is quite time consuming.  As it is one "arm" it is all
beneath one subtree.  But still split to several code blocks.
In that case it would be really handy to say :noexport: to the subtree
to
(1) not execute the lengthy code
(2) simultaneously omit the section in the exported pdf

Note, that I am also aware of the caching system.  I have been using it
a lot, but it sort of breaks the reproducible research paradigm and got
into my way too often.
>
>> In my opinion, these #+calls should not be evaluated.
>
> I really don't have any strong opinion about this, even if, without further
> thinking, I'd favor the same behavior as the one you expected.
>
> Best regards,
>   Seb
>
> [1] Notice the different spelling: with or without the dash.

next prev parent reply	other threads:[~2012-09-05 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  7:59 [Bug] [babel] calls in :noexport: subtrees evaluated Andreas Leha
2012-09-05 11:59 ` Sebastien Vauban
2012-09-05 12:15   ` Andreas Leha [this message]
2012-09-05 12:37   ` Nicolas Goaziou
2012-09-05 13:12     ` Andreas Leha
2012-09-05 16:17     ` Sebastien Vauban
2012-09-05 16:40       ` Eric Schulte
2012-09-05 18:53         ` Andreas Leha
2012-09-05 19:39         ` Sebastien Vauban

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=87oblkbr8m.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.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

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).