From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: Pattch to org.texi: Document ":eval no" Date: Thu, 28 Jul 2011 15:09:29 +0200 Message-ID: <801uxaimba.fsf@somewhere.org> References: <31634.1311855046@maps> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Stephen, Stephen Eglen wrote: > 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 While this -- really! -- is an excellent initiative (to update the doc when you notice something's missing). Note that, would have better read my notes, instead of counting on my memory, I would have told you ":eval never". Though, I just checked, and confirm that ":eval no" is (for the moment) equivalent to it: see ob.el, lines 218 and 226. So, this patch makes sense -- except if Eric wants to let this option disappear, and only supports it in the code for backward compatibility. Best regards, Seb -- Sebastien Vauban