From: Kyle Meyer <kyle@kyleam.com>
To: Mackenzie Bligh <mackenziebligh@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Contribution of a :confirm-evaluate flag to src blocks
Date: Thu, 18 Jul 2019 00:09:52 -0400 [thread overview]
Message-ID: <87sgr4htkf.fsf@kyleam.com> (raw)
In-Reply-To: <CACoFLrOvXMRK4DqfxR6GyMLjowSC2b71=FCeioxjH=mMRUBvtg@mail.gmail.com>
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
next prev parent reply other threads:[~2019-07-18 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 18:30 Contribution of a :confirm-evaluate flag to src blocks Mackenzie Bligh
2019-07-18 4:09 ` Kyle Meyer [this message]
2019-07-18 17:10 ` Mackenzie Bligh
2019-07-18 19:21 ` Kyle Meyer
2019-07-18 21:53 ` Berry, Charles
2019-07-18 22:11 ` Kyle Meyer
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=87sgr4htkf.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=mackenziebligh@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).