emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Pattch to org.texi: Document ":eval no"
Date: Thu, 28 Jul 2011 15:09:29 +0200	[thread overview]
Message-ID: <801uxaimba.fsf@somewhere.org> (raw)
In-Reply-To: 31634.1311855046@maps

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

next prev parent reply	other threads:[~2011-07-28 13:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 12:10 Pattch to org.texi: Document ":eval no" Stephen Eglen
2011-07-28 13:09 ` Sebastien Vauban [this message]
2011-07-28 22:57   ` Eric Schulte
2011-08-16 16:45 ` Bastien
2011-08-16 21:40   ` Stephen Eglen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=801uxaimba.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).