From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Running babel blocks in :noexport: sections Date: Sun, 28 Oct 2012 15:22:59 -0500 Message-ID: References: <87mwz7r09r.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41668) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSZNu-0006r7-7t for emacs-orgmode@gnu.org; Sun, 28 Oct 2012 16:23:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TSZNt-0003Fg-1c for emacs-orgmode@gnu.org; Sun, 28 Oct 2012 16:23:02 -0400 Received: from mail-ob0-f169.google.com ([209.85.214.169]:39591) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSZNs-0003Fc-Rh for emacs-orgmode@gnu.org; Sun, 28 Oct 2012 16:23:00 -0400 Received: by mail-ob0-f169.google.com with SMTP id va7so4585179obc.0 for ; Sun, 28 Oct 2012 13:23:00 -0700 (PDT) In-Reply-To: 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@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: emacs-orgmode 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 >>