Andreas Leha <andreas.l...@med.uni-goettingen.de> writes:
> Hi Eric,
>
> Eric Schulte <schulte.e...@gmail.com> writes:
>
>>>>>>
>>>>>> So what is your suggestion for the OP to achieve what he is after?
>>>>>> noexport and noeval at the same time.
>>>>>>
>>
>> I'm jumping in half way through here,
>
> Thanks for jumping in.
>
>> but wouldn't setting the :noeval
>> property to "yes" and :export property to "none" on the subtree work?
>
> Well, the property-setting works, but that is really cumbersome. In a
> typical org file, it takes 5 keystrokes to toggle the :noexport: tag
> (C-c C-c n TAB RET). But I do not want to count the keystrokes it take
> to additionally set these properties.
>
Not that bad "C-c C-x p n RET yes", I get 8 to set noeval, if you've
done it already in that Org file. You could also easily wrap this
behavior into a function and bind that to a key-chord.
>
> Just to confirm. This is what you suggest, correct?
>
> --8<---------------cut here---------------start------------->8---
> * test
>
> ** Not exported
> :noexport:
> :PROPERTIES:
> :noeval: "yes"
> :export: "none"
> :END:
> #+BEGIN_SRC ditaa :file test.png :cmdline -E
> +--------+---+---+---+---+---+---+---+
> +---+---+---+---+---+---+---+---+
> x | 0 cRED | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | 1 | 0 | 1
> | 1 |
> +--------+---+---+---+---+---+---+---+
> +---+---+---+---+---+---+---+---+
> #+END_SRC
>
> ** blah blah
> blah blah blah
> --8<---------------cut here---------------end--------------->8---
>
>
>
>>
>> One may also want to COMMENT the subtree to inhibit it's export
>> wholepiece (not just code blocks).
>
> This does not seem to work, as the test.png is also created here.
>
> Again, just to confirm. This is your suggestion, correct?
>
> --8<---------------cut here---------------start------------->8---
> * test
>
> ** COMMENT Not exported
> #+BEGIN_SRC ditaa :file test.png :cmdline -E
> +--------+---+---+---+---+---+---+---+
> +---+---+---+---+---+---+---+---+
> x | 0 cRED | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | 1 | 0 | 1
> | 1 |
> +--------+---+---+---+---+---+---+---+
> +---+---+---+---+---+---+---+---+
> #+END_SRC
>
> ** blah blah
> blah blah blah
> --8<---------------cut here---------------end--------------->8---
>
Close, I meant the following alternative
--8<---------------cut here---------------start------------->8---
* test
** COMMENT Not exported
:PROPERTIES:
:noeval: "yes"
:END:
#+BEGIN_SRC ditaa :file test.png :cmdline -E
+--------+---+---+---+---+---+---+---+
+---+---+---+---+---+---+---+---+
x | 0 cRED | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 0 | 0 | 0 | 1 | 0 | 1 |
1 |
+--------+---+---+---+---+---+---+---+
+---+---+---+---+---+---+---+---+
#+END_SRC
** blah blah
blah blah blah
--8<---------------cut here---------------end--------------->8---
>
>
> So, my question to this thread is: What is the easiest way to disable a
> subtree during export completely so that also none of the code blocks is
> evaluated (regardless of its :session argument).
>
My example immediately above.
>
> Or even more precisely: Couldn't the COMMENT keyword do exactly that? I
> do not expect code from inside a COMMENT subtree to be considered during
> export.
>
No. This has been raised previously and there was a consensus that it
is often desirable for code in a COMMENT section to be evaluated on
export. Personally I often stuff code blocks into COMMENT sections
which I want run as part of my publishing process (e.g., to create
resources used in the exported document).
Best,
>
>
> Regards,
> Andreas
>
>
>
>
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
