Re: [O] Running babel blocks in :noexport: sections
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? What behavior do you get when running with emacs -Q? -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Running babel blocks in :noexport: sections
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, 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 setup :noexport: >>> >>> #+begin_src R :session r >>> >>> load libraries >>> read data files >>> do universal operations >>> >>> #+end_src >>> >>> * Slide >>> >>> #+begin_src R :session r :exports results :results output graphics >>> >>> subset(larger_data_set_from_above) >>> processing >>> plot something >>> >>> #+end_src >>> >>> I noticed today that my :noexport: setup sections (I had a couple) >>> were not updating. I re-defined a variable name further down in my >>> file and it was re-using the definition from an above setup section >>> (tagged with :noexport:). Just because I don't want it export doesn't >>> mean I don't want to have useful stuff in the headline... >>> >>> 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. >>> >>> >>> Thanks for any input, >>> John >>> >> >> Instead of tagging the headline as :noexport: you can add the COMMENT >> flag to it. This should result in your desired behavior. See the >> attached example. >> >> > > Brilliant. That'll do just fine. Never knew about that! > > John > >> >> -- >> Eric Schulte >> http://cs.unm.edu/~eschulte >>
Re: [O] Running babel blocks in :noexport: sections
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 setup :noexport: >> >> #+begin_src R :session r >> >> load libraries >> read data files >> do universal operations >> >> #+end_src >> >> * Slide >> >> #+begin_src R :session r :exports results :results output graphics >> >> subset(larger_data_set_from_above) >> processing >> plot something >> >> #+end_src >> >> I noticed today that my :noexport: setup sections (I had a couple) >> were not updating. I re-defined a variable name further down in my >> file and it was re-using the definition from an above setup section >> (tagged with :noexport:). Just because I don't want it export doesn't >> mean I don't want to have useful stuff in the headline... >> >> 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. >> >> >> Thanks for any input, >> John >> > > Instead of tagging the headline as :noexport: you can add the COMMENT > flag to it. This should result in your desired behavior. See the > attached example. > > Brilliant. That'll do just fine. Never knew about that! John > > -- > Eric Schulte > http://cs.unm.edu/~eschulte >
Re: [O] Running babel blocks in :noexport: sections
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 libraries > read data files > do universal operations > > #+end_src > > * Slide > > #+begin_src R :session r :exports results :results output graphics > > subset(larger_data_set_from_above) > processing > plot something > > #+end_src > > I noticed today that my :noexport: setup sections (I had a couple) > were not updating. I re-defined a variable name further down in my > file and it was re-using the definition from an above setup section > (tagged with :noexport:). Just because I don't want it export doesn't > mean I don't want to have useful stuff in the headline... > > 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. > > > Thanks for any input, > John > Instead of tagging the headline as :noexport: you can add the COMMENT flag to it. This should result in your desired behavior. See the attached example. #+Title: example * COMMENT not exported but run #+name: the-date #+begin_src sh date #+end_src * exported and able to call into un-exported subtrees The date today is, #+call: the-date() -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Running babel blocks in :noexport: sections
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 export engine. The current exporter removes :noexport: sections before executing src blocks within (it always did). Regards, -- Nicolas Goaziou
