emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Mackenzie Bligh <mackenziebligh@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Contribution of a :confirm-evaluate flag to src blocks
Date: Wed, 17 Jul 2019 11:30:38 -0700	[thread overview]
Message-ID: <CACoFLrOvXMRK4DqfxR6GyMLjowSC2b71=FCeioxjH=mMRUBvtg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]

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 "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 believe
that this is a safer behavior compared to disabling "ask-to-execute" on a
per language basis, and adds convenience to src blocks for literate
programming. Thanks for your time, and I welcome any feedback!

Sincerely,

Mack

[-- Attachment #1.2: Type: text/html, Size: 1212 bytes --]

[-- Attachment #2: 0001-ob-core.el-Add-confirm-evaluate-flag-to-src-blocks.patch --]
[-- Type: application/x-patch, Size: 1781 bytes --]

next             reply	other threads:[~2019-07-17 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 18:30 Mackenzie Bligh [this message]
2019-07-18  4:09 ` Contribution of a :confirm-evaluate flag to src blocks Kyle Meyer
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='CACoFLrOvXMRK4DqfxR6GyMLjowSC2b71=FCeioxjH=mMRUBvtg@mail.gmail.com' \
    --to=mackenziebligh@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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

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).