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

From: "Eric Schulte" <schulte.eric@gmail.com>
To: Lawrence Mitchell <wence@gmx.li>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: evaluating all R code blocks (newbie question)
Date: Thu, 20 Jan 2011 09:22:27 -0700	[thread overview]
Message-ID: <8739onzg2u.fsf@gmail.com> (raw)
In-Reply-To: m3ei87imzx.fsf@gmx.li

Lawrence Mitchell <wence@gmx.li> writes:

> Julian Burgos wrote:
>> Many thanks Lawrence.  Yes, I'm aware of the risks, but for now I am
>> only working with my own files.
>> Do you know if it is possible to evaluation confirmation as a header
>> option, so I can left it on but turn it off in my own files?
>
> I don't believe it is.  If you think about, this is also a
> security hole, since a malicious user could put the relevant
> header in, even if you've set org-confirm-babel-evaluate to t.
>

Indeed this is the case, the :eval header argument [1] can be used
inhibit the evaluation of some code blocks, if the user already has

  (setq org-confirm-babel-evaluate nil)

but it can not be used to remove the need for confirmation of code block
evaluation when the user has

  (setq org-confirm-babel-evaluate t)

For security reasons.

Personally I don't require confirmation of evaluation as I find that I
both trust everyone sharing org-mode files with me, and generally I read
code blocks before I evaluate them.

Best -- Eric

Footnotes: 
[1]  http://orgmode.org/manual/eval.html

next prev parent reply	other threads:[~2011-01-20 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 15:04 evaluating all R code blocks (newbie question) Julian Burgos
2011-01-20 15:38 ` Lawrence Mitchell
2011-01-20 15:53   ` Julian Burgos
2011-01-20 16:00     ` Lawrence Mitchell
2011-01-20 16:19       ` Julian Burgos
2011-01-20 16:22       ` Eric Schulte [this message]
2011-01-21  0:20 ` Leo Alekseyev

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=8739onzg2u.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wence@gmx.li \
    /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).