From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: [org-babel] switching off (re-)evaluation of code blocks during Org export Date: Tue, 22 Nov 2011 10:31:33 -0700 Message-ID: <87aa7o5aiy.fsf@gmail.com> References: <2A2CA71C-50E6-4533-BD40-2D879EF3BBCC@beds.ac.uk> <87aa7plzl8.fsf@gmail.com> <8062ictrp3.fsf@somewhere.org> <87ty5w5dzs.fsf@gmail.com> <87ehx02i44.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:58902) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RSuC4-00064K-C7 for emacs-orgmode@gnu.org; Tue, 22 Nov 2011 12:31:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RSuC2-00081T-QS for emacs-orgmode@gnu.org; Tue, 22 Nov 2011 12:31:40 -0500 Received: from mail-iy0-f169.google.com ([209.85.210.169]:49119) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RSuC2-00081G-NQ for emacs-orgmode@gnu.org; Tue, 22 Nov 2011 12:31:38 -0500 Received: by iaek3 with SMTP id k3so646378iae.0 for ; Tue, 22 Nov 2011 09:31:38 -0800 (PST) In-Reply-To: <87ehx02i44.fsf@norang.ca> (Bernt Hansen's message of "Tue, 22 Nov 2011 12:15:55 -0500") 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: Bernt Hansen Cc: Sebastien Vauban , emacs-orgmode@gnu.org Bernt Hansen writes: > Eric Schulte writes: > >>> >>> Hence, maybe we should be able to set 2 possible behaviors[1] for the >>>`eval' >>> parameter: >>> >>> - one for the interactive mode (yes/query/no), and >>> - one for the export mode (yes/no, and maybe query as well?). >>> >> >> Agreed, >> >> The eval header argument now supports the following four options >> (updated in the manual under "Specific header arguments"). >> >> | no or never | no evaluation anytime | >> | query | query before evaluation anytime | >> | no-eval or never-eval | no evaluation during export | >> | query-eval | query before evaluation during export | >> >> Thanks for the suggestion > > Hi Eric, > > Should the last two be named export-no, export-never, and export-query. > That seems more self-documenting to me. > Oh!, I miss-typed the above it should read as follows. | no or never | no evaluation anytime | | query | query before evaluation anytime | | no-export or never-export | no evaluation during export | | query-export | query before evaluation during export | Thanks for catching this, the documentation has the correct terms. Best, > > I'm going to be confused about the difference between 'no' and 'no-eval' > in the future. Since the eval header argument already has 'eval' in it > is it not more useful to specify these values are export related? > > Regards, > Bernt -- Eric Schulte http://cs.unm.edu/~eschulte/