[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Contribution of a :confirm-evaluate flag to src blocks

From: Berry, Charles
Subject: Re: [O] Contribution of a :confirm-evaluate flag to src blocks
Date: Thu, 18 Jul 2019 21:53:13 +0000


I think you have stepped onto a slippery slope.

Adding an :eval option that turns off confirmation queries without user 
intervention defeats the security purpose stated for 

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. 

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

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



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

> On Jul 18, 2019, at 12:21 PM, Kyle Meyer <address@hidden> wrote:
> Mackenzie Bligh <address@hidden> writes:
>> Do you have any suggestions for the name of such a value?
> I tried to avoid being responsible for a poorly chosen name :]
> "'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'?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]