From: Kyle Meyer <firstname.lastname@example.org>
To: 吴锐扬 <email@example.com>
Cc: "Berry, Charles" <firstname.lastname@example.org>,
Subject: Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls
Date: Wed, 28 Oct 2020 23:16:32 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
> The author explained his motivation for the commit in the mailing list before it got applied:
>> That's because lob calls get wrapped internally in an anonymous
>> emacs-lisp source block that then feeds through the result from the
>> actual call as elisp. The attached patch should suppress the
>> confirmation for the wrapper call. To the best of my knowledge nothing
>> dangerous can happen with that evaluation and all confirmations for the
>> call stack down from there have already taken place according to the
>> users' setup.
Just for reference: it looks like that's
> If I understand correctly, executing a lob call would trigger two user
> confirmations in the past, and this commit was meant to suppress one
> of the two confirmations. (I may be wrong since I am a fairly new user
> of org mode.)
Thanks for digging. Indeed, if you go back to the parent of 56bf3d789
(Babel: avoid superfluous confirmation for internal wrapper,
2013-04-10), there are two queries. On that commit, there is one.
> Now there is no confirmation at all. IMHO, there should be exactly
> one confirmation ideally.
It looks like the query went away with dbb375fdf (Simplify Babel calls
evaluation, 2016-06-16), which was included in the 9.0 release. Based
on a quick glance at that commit, I don't think that was an intentional
I won't take a closer look at this until at least this weekend, though.
I'd be very happy if someone beat me to it.
next prev parent reply other threads:[~2020-10-29 3:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 20:18 Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls 吴锐扬
2020-10-27 17:47 ` 吴锐扬
2020-10-28 11:32 ` Eric S Fraga
2020-10-28 17:26 ` Berry, Charles via General discussions about Org-mode.
2020-10-29 1:29 ` 吴锐扬
2020-10-29 3:16 ` Kyle Meyer [this message]
2020-10-29 17:17 ` Berry, Charles via General discussions about Org-mode.
2020-11-01 23:44 ` Kyle Meyer
2020-11-02 0:41 ` 吴锐扬
2020-10-29 19:05 ` Achim Gratz
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).