From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Pattch to org.texi: Document ":eval no" Date: Thu, 28 Jul 2011 16:57:59 -0600 Message-ID: <877h72dk41.fsf@gmail.com> References: <31634.1311855046@maps> <801uxaimba.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:42230) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qmacp-0003Ci-4N for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 20:08:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qmacn-0002X0-Jj for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 20:08:23 -0400 Received: from mail-pz0-f49.google.com ([209.85.210.49]:61195) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qmacn-0002Wc-E3 for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 20:08:21 -0400 Received: by pzk33 with SMTP id 33so4602614pzk.8 for ; Thu, 28 Jul 2011 17:08:19 -0700 (PDT) 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: Sebastien Vauban Cc: emacs-orgmode@gnu.org Applied, Thanks for the patch -- Eric "Sebastien Vauban" writes: > 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 -- Eric Schulte http://cs.unm.edu/~eschulte/