From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernt Hansen <bernt@norang.ca>
Subject: Re: [org-babel] switching off (re-)evaluation of code blocks during
 Org export
Date: Tue, 22 Nov 2011 12:15:55 -0500
Message-ID: <87ehx02i44.fsf@norang.ca>
References: <2A2CA71C-50E6-4533-BD40-2D879EF3BBCC@beds.ac.uk>
	<87aa7plzl8.fsf@gmail.com> <8062ictrp3.fsf@somewhere.org>
	<87ty5w5dzs.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:53875)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1RStx3-0006kB-MZ
	for emacs-orgmode@gnu.org; Tue, 22 Nov 2011 12:16:15 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1RStx2-0004uu-CJ
	for emacs-orgmode@gnu.org; Tue, 22 Nov 2011 12:16:09 -0500
Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:18205)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1RStx2-0004td-1C
	for emacs-orgmode@gnu.org; Tue, 22 Nov 2011 12:16:08 -0500
In-Reply-To: <87ty5w5dzs.fsf@gmail.com> (Eric Schulte's message of "Tue, 22
	Nov 2011 07:02:29 -0700")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <schulte.eric@gmail.com>
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org

Eric Schulte <schulte.eric@gmail.com> 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.

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