From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Berry, Charles" <ccberry@ucsd.edu>
Subject: Re: Contribution of a :confirm-evaluate flag to src blocks
Date: Thu, 18 Jul 2019 21:53:13 +0000
Message-ID: <8EC8C20C-3E43-4E72-98A7-D9415D4740F6@ucsd.edu>
References: <CACoFLrOvXMRK4DqfxR6GyMLjowSC2b71=FCeioxjH=mMRUBvtg@mail.gmail.com>
 <87sgr4htkf.fsf@kyleam.com>
 <CACoFLrN3m9UL_jiSMFGrimctrKc6=JmKmNpZLO5c=7kxG5zffg@mail.gmail.com>
 <87blxrdu8e.fsf@kyleam.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:53730)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <ccberry@ucsd.edu>) id 1hoEuy-0004Kp-Gj
 for emacs-orgmode@gnu.org; Thu, 18 Jul 2019 18:30:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <ccberry@ucsd.edu>) id 1hoEux-0005Wy-ED
 for emacs-orgmode@gnu.org; Thu, 18 Jul 2019 18:30:28 -0400
Received: from mx0b-00395d01.pphosted.com ([148.163.137.170]:58878)
 by eggs.gnu.org with esmtp (Exim 4.71)
 (envelope-from <ccberry@ucsd.edu>) id 1hoEux-0005Wb-4r
 for emacs-orgmode@gnu.org; Thu, 18 Jul 2019 18:30:27 -0400
In-Reply-To: <87blxrdu8e.fsf@kyleam.com>
Content-Language: en-US
Content-ID: <2FBF45B99A93324DA8302378E7EE76D5@AD.UCSD.EDU>
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: <https://lists.gnu.org/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"
 <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Mackenzie Bligh <mackenziebligh@gmail.com>, "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>

Gentlemen,

I think you have stepped onto a slippery slope.

Adding an :eval option that turns off confirmation queries without user int=
ervention defeats the security purpose stated for `org-confirm-babel-evalua=
te'.

Likewise, adding a new header argument that turns off such checks may have =
pernicious effects.

A better option IMO is to use existing features of babel to accomplish the =
end you desire.=20

A simple option is to have a src block that let binds org-confirm-babel-eva=
luate to nil, then navigates to and executes another src block that contain=
s noweb statements that execute other blocks. The user is prompted just onc=
e and the global behavior of `org-confirm-babel-evaluate' is unaltered.

There are many ways to achieve this kind of behavior and/or fine tune the p=
rompting behavior with existing babel capabilities.

HTH,

Chuck

p.s. I do not get what is `too crude' about using `org-confirm-babel-evalua=
te'. Maybe an ECM would help others understand what motivates this judgment=
.

> On Jul 18, 2019, at 12:21 PM, Kyle Meyer <kyle@kyleam.com> wrote:
>=20
> Mackenzie Bligh <mackenziebligh@gmail.com> writes:
>=20
>> Do you have any suggestions for the name of such a value?
>=20
> I tried to avoid being responsible for a poorly chosen name :]
>=20
> "'yes' or 'always'" pairs well with the existing "'no' or 'never'", but
> I suppose that risks users not realizing that it implies not querying.
> Perhaps 'eval-no-query', 'eval-without-query', or just 'without-query'?
>=20
>=20