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. 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.) Now there is no confirmation at all. IMHO, there should be exactly one confirmation ideally. But you are right, I should just copy the author on this. Thanks, Ruiyang > On Oct 28, 2020, at 10:26 AM, Berry, Charles <ccbe...@health.ucsd.edu> wrote: > > FWIW, it doesn't seem like an accident. You might ping the author of this > commit: > > $ git log -S "(let (org-confirm-babel-evaluate)" > commit 56bf3d789146fcd3c9f82d875de28c394fe593a0 > Author: Achim Gratz <strom...@stromeko.de> > Date: Wed Apr 10 20:28:31 2013 +0200 > > Babel: avoid superfluous confirmation for internal wrapper > > * lisp/ob-exp.el (org-babel-exp-results): Suppress user confirmation > of the emacs-lisp wrapper execution around a lob call. > > * lisp/ob-lob.el (org-babel-lob-execute): Suppress user confirmation > of the emacs-lisp wrapper execution around a lob call. > > > > HTH, > > Chuck > >> On Oct 28, 2020, at 4:32 AM, Eric S Fraga <e.fr...@ucl.ac.uk> wrote: >> >> On Wednesday, 14 Oct 2020 at 16:18, 吴锐扬 wrote: >>> I have org-confirm-babel-evaluate set to t by default. With this, I >>> expect to be queried with the execution of every code block or lob >>> call. However, this does not happen when exporting lob calls (to latex >>> for example). Here is an example: >> >> Confirmed with fairly recent org from git with >> org-confirm-babel-evaluate set to t. Does seem a little strange. It >> doesn't bother me much as I don't export org files that I haven't >> created myself but it does appear to be a hole. >> >> -- >> : Eric S Fraga via Emacs 28.0.50, Org release_9.4-61-ga88806.dirty >> >> >