Gentlemen,
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
`org-confirm-babel-evaluate'.
Likewise, adding a new header argument that turns off such checks may have
pern
Hi Chuck,
"Berry, Charles" writes:
> 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
> `org-confirm-babel-evaluate'.
>
> Likewise, adding a new header argument tha
Mackenzie Bligh 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.
Perha
Hi Kyle,
I didn't think of that, but that's a really good idea! Do you have any
suggestions for the name of such a value?
On Wed, Jul 17, 2019 at 9:09 PM Kyle Meyer wrote:
> Hi Mackenzie,
>
> Mackenzie Bligh writes:
>
> > First time contributing here, so apologies if I haven't gotten this quit
Hi Mackenzie,
Mackenzie Bligh writes:
> First time contributing here, so apologies if I haven't gotten this quite
> right.
Great, thanks for sending the patch!
> The results of some
> of these src blocks are fed into other src blocks, and having to input "y"
> multiple times when trying to hit
Hi All,
First time contributing here, so apologies if I haven't gotten this quite
right. As part of my employment I have an org document I have written
contains a number of restclient and bash code blocks. The results of some
of these src blocks are fed into other src blocks, and having to input "
