From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Subject: Pattch to org.texi: Document ":eval no"
Date: Thu, 28 Jul 2011 13:10:46 +0100
Message-ID: <31634.1311855046@maps>
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:44631)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sje30@damtp.cam.ac.uk>) id 1QmPQO-000842-EE
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 08:10:49 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <sje30@damtp.cam.ac.uk>) id 1QmPQN-0003rb-Fx
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 08:10:48 -0400
Received: from ppsw-51.csi.cam.ac.uk ([131.111.8.151]:37651)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sje30@damtp.cam.ac.uk>) id 1QmPQN-0003rX-7m
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 08:10:47 -0400
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: </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: emacs-orgmode@gnu.org
Cc: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>

Small patch attached, thanks Seb for pointing this out.

Stephen

diff --git a/doc/org.texi b/doc/org.texi
index 3ecf897..eb45885 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -12990,10 +12990,10 @@ permissions of the tangled file are set to make it executable.
 @subsubsection @code{:eval}
 The @code{:eval} header argument can be used to limit the evaluation of
 specific code blocks.  @code{:eval} accepts two arguments ``never'' and
-``query''.  @code{:eval never} will ensure that a code block is never
-evaluated, this can be useful for protecting against the evaluation of
-dangerous code blocks.  @code{:eval query} will require a query for every
-execution of a code block regardless of the value of the
+``query''.  @code{:eval never} (or @code{:eval no}) will ensure that a code
+block is never evaluated, this can be useful for protecting against the
+evaluation of dangerous code blocks.  @code{:eval query} will require a query
+for every execution of a code block regardless of the value of the
 @code{org-confirm-babel-evaluate} variable.
 
 If this header argument is not set then evaluation is determined by the value