From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [Bug] [babel] calls in :noexport: subtrees evaluated Date: Wed, 05 Sep 2012 13:59:19 +0200 Message-ID: <80y5ko3cko.fsf@somewhere.org> References: <87ipbtc5q0.fsf@med.uni-goettingen.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org 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). > 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. -- Sebastien Vauban