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 18:17:44 +0200 Message-ID: <80zk541m1j.fsf@somewhere.org> References: <87ipbtc5q0.fsf@med.uni-goettingen.de> <80y5ko3cko.fsf@somewhere.org> <87zk54ejc4.fsf@gmail.com> 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 Hi Nicolas, Nicolas Goaziou wrote: > "Sebastien Vauban" writes: >> 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). >> >> 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. > > 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. To see whether there is more weigh toward a solution or the other, I would formulate the question this way: are there real use-cases where one would want to *not* export a subtree (by tagging it), though to *well* evaluate the code blocks it contains? If the answer is yes, then, definitely, both things must really stay separated. Best regards, Seb -- Sebastien Vauban