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 21:39:37 +0200 Message-ID: <80vcfs1cp2.fsf@somewhere.org> References: <87ipbtc5q0.fsf@med.uni-goettingen.de> <80y5ko3cko.fsf@somewhere.org> <87zk54ejc4.fsf@gmail.com> <80zk541m1j.fsf@somewhere.org> <87r4qgqr2i.fsf@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 Eric, Eric Schulte wrote: > "Sebastien Vauban" writes: >> Nicolas Goaziou wrote: >>> "Sebastien Vauban" writes: >>>> In fact, what you expect is that putting a tag ":noexport:" on a subtr= ee would >>>> propagate the option ":eval no-export"[1] to all code blocks beneath i= t. 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 fu= rther >>>> 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 wou= ld >> formulate the question this way: >> >> are there real use-cases where one would want to *not* export a subt= ree >> (by tagging it), though to *well* evaluate the code blocks it contai= ns? > > #+Title: Example > > Results in heading "first" are generated by un-exported code blocks in > heading "second". > > * first > > Things my adviser cares about. > > #+RESULTS: foo > : like some result: 3 > > * second :noexp= ort: > > Things my adviser does not care about, but which I need to keep, like > minutiae of generating the result. > > #+Name: bar > - foo > - bar > - baz > > #+Name: foo > #+begin_src sh :var bar=3Dbar > echo "like some result: $(echo $bar|wc -w)" > #+end_src Accepted!=C2=A0;-) Best regards, Seb PS- Woudn't it be good if we standardize the "noexport"/"no-export" thing? Have both the same (tag and property value)? --=20 Sebastien Vauban