John Hendy writes:
> Just kidding... just checked *Messages* buffer, and all the headlines
> I converted to COMMENT headlines are *not* executing the enclosed
> babel blocks.
>
> Is there a setting for this you have and I don't?
>
Not that I know of.
Are you using the new or the old exporter?
Just kidding... just checked *Messages* buffer, and all the headlines
I converted to COMMENT headlines are *not* executing the enclosed
babel blocks.
Is there a setting for this you have and I don't?
John
On Sun, Oct 28, 2012 at 12:23 PM, John Hendy wrote:
> On Sat, Oct 27, 2012 at 5:57 PM, Er
On Sat, Oct 27, 2012 at 5:57 PM, Eric Schulte wrote:
> John Hendy writes:
>
>> For papers and beamer presentations, I sometimes hide more "universal"
>> babel blocks inside a sort of setup headline. I thought I'd done this
>> before, but perhaps not... The idea would be like so:
>>
>> * Data setu
John Hendy writes:
> For papers and beamer presentations, I sometimes hide more "universal"
> babel blocks inside a sort of setup headline. I thought I'd done this
> before, but perhaps not... The idea would be like so:
>
> * Data setup :noexport:
>
> #+begin_src R :session r
>
> load librari
Hello,
John Hendy writes:
> Is this a bug/inappropriate setting, desirable based on how others use
> :noexport: headlines, or would others see value in executing babel
> blocks in :noexport: headlines?
>
> If I /didn't/ want it executed, I'd use :execute no.
This is the behaviour of the new exp
For papers and beamer presentations, I sometimes hide more "universal"
babel blocks inside a sort of setup headline. I thought I'd done this
before, but perhaps not... The idea would be like so:
* Data setup :noexport:
#+begin_src R :session r
load libraries
read data files
do universal oper
