From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [Bug] [babel] calls in :noexport: subtrees evaluated
Date: Wed, 05 Sep 2012 14:37:47 +0200 [thread overview]
Message-ID: <87zk54ejc4.fsf@gmail.com> (raw)
In-Reply-To: <80y5ko3cko.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 05 Sep 2012 13:59:19 +0200")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> 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.
As far as the new exporter goes (you may want to have a look at
`org-export-as' function), the order is:
- Process macros.
- Expand #+INCLUDE: keywords.
- Evaluate code blocks.
Note that "noexport" sub-trees are not inhibited. The are just skipped
when the parse tree is processed.
To answer the OP, :noexport: tag is related to export, not to
src-blocks. There are already other ways to disable code evaluation on
subtrees. It may be useful, as in your case, to have their behaviour
linked, but again, sometimes not.
It's often better to keep separate things, well, separate.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-09-05 12:42 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
2012-09-05 12:37 ` Nicolas Goaziou [this message]
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=87zk54ejc4.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.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).