Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-11-01 Thread 吴锐扬
Can confirm that. Thanks for your work! Best, Ruiyang > On Nov 1, 2020, at 4:44 PM, Kyle Meyer wrote: > > Kyle Meyer writes: > >> 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

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-11-01 Thread Kyle Meyer
Kyle Meyer writes: > 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 > change. > > I won't take a closer look at this until at

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-29 Thread Achim Gratz
Berry, Charles" via "General discussions about Org-mode. writes: > FWIW, it doesn't seem like an accident. You might ping the author of this > commit: No, that change was to suppress an _additional_ confirmation that was triggered by some internal implementation details. Regards, Achim. --

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-29 Thread Berry, Charles
Just on a whim, I changed `org-babel-exp-results' by deleting (let (org-confirm-babel-evaluate-NOT) and the matching right parenthesis. Now I get a single prompt to confirm evaluation using Ruiyang's ECM. HTH, Chuck > On Oct 28, 2020, at 8:16 PM, Kyle Meyer wrote: > > 吴锐扬 writes: > >>

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-28 Thread Kyle Meyer
吴锐扬 writes: > 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

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-28 Thread 吴锐扬
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 >

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-28 Thread Berry, Charles
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 Date: Wed Apr 10 20:28:31 2013 +0200 Babel: avoid superfluous confirmation for internal

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-28 Thread Eric S Fraga
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:

Re: Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-27 Thread 吴锐扬
This is just a follow up to see if anyone have insights on this matter. Thanks Ruiyang > On Oct 14, 2020, at 1:18 PM, 吴锐扬 wrote: > > Hi, > > 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,

Confusion about org-confirm-babel-evaluate's behavior while exporting lob calls

2020-10-14 Thread 吴锐扬
Hi, 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: __ 1.