From: Eric Schulte <eric.schulte@gmx.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Bug] [babel] calls in :noexport: subtrees evaluated
Date: Wed, 05 Sep 2012 10:40:27 -0600 [thread overview]
Message-ID: <87r4qgqr2i.fsf@gmx.com> (raw)
In-Reply-To: 80zk541m1j.fsf@somewhere.org
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> 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?
>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: example.org --]
[-- Type: text/x-org, Size: 592 bytes --]
#+Title: Example
Results in heading [[#first]] are generated by un-exported code blocks in
heading [[#second]].
* first
:PROPERTIES:
:CUSTOM_ID: first
:END:
Things my adviser cares about.
#+RESULTS: foo
: like some result: 3
* second :noexport:
:PROPERTIES:
:CUSTOM_ID: second
:END:
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=bar
echo "like some result: $(echo $bar|wc -w)"
#+end_src
[-- Attachment #3: Type: text/plain, Size: 46 bytes --]
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2012-09-05 18:11 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
2012-09-05 13:12 ` Andreas Leha
2012-09-05 16:17 ` Sebastien Vauban
2012-09-05 16:40 ` Eric Schulte [this message]
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=87r4qgqr2i.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).