From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kyle Meyer <kyle@kyleam.com>
Subject: Re: Contribution of a :confirm-evaluate flag to src blocks
Date: Thu, 18 Jul 2019 00:09:52 -0400
Message-ID: <87sgr4htkf.fsf@kyleam.com>
References: <CACoFLrOvXMRK4DqfxR6GyMLjowSC2b71=FCeioxjH=mMRUBvtg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:46064)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <kyle@kyleam.com>) id 1hnxjw-0000lM-M2
 for emacs-orgmode@gnu.org; Thu, 18 Jul 2019 00:09:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <kyle@kyleam.com>) id 1hnxjv-0007Tq-LH
 for emacs-orgmode@gnu.org; Thu, 18 Jul 2019 00:09:56 -0400
Received: from pb-smtp2.pobox.com ([64.147.108.71]:64379)
 by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <kyle@kyleam.com>) id 1hnxjv-0007TW-5m
 for emacs-orgmode@gnu.org; Thu, 18 Jul 2019 00:09:55 -0400
In-Reply-To: <CACoFLrOvXMRK4DqfxR6GyMLjowSC2b71=FCeioxjH=mMRUBvtg@mail.gmail.com>
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: Mackenzie Bligh <mackenziebligh@gmail.com>, emacs-orgmode@gnu.org

Hi Mackenzie,

Mackenzie Bligh <mackenziebligh@gmail.com> 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 a REST api quickly became cumbersome. I
> also found the method of supplying a new org-confirm-babel-evaluate to
> disable the "ask to execute" behavior on a per language basis to be too
> crude. Therefore, I would like to introduce a new flag for src blocks
> ":confirm-evaluate", where a value of "n", "no", "f", or "false" will
> disable the "ask to execute" behavior for that specific block.

I'm not much of a Babel user, but I wonder whether a better option would
be to extend :eval with a value that means "eval but don't query".
org-babel-check-confirm-evaluate could then consider this when binding
`query'.  That seems like it would serve the same purpose while avoiding
adding a new header argument.

What do you think?

-- 
Kyle