Here's the output of git bisect.
38be85124551083d26981ab3c22d7b09632b7b10 is the first bad commit
commit 38be85124551083d26981ab3c22d7b09632b7b10
Author: Nicolas Goaziou <m...@nicolasgoaziou.fr>
Date: Fri Dec 22 00:06:39 2017 +0100
ob-core: Do not always evaluate Lisp code in parameters
* lisp/ob-core.el (org-babel-get-src-block-info):
(org-babel-params-from-properties):
(org-babel-parse-header-arguments): Add optional argument disabling
Lisp evaluation in parameters.
lisp/ob-core.el | 51 ++++++++++++++++++++++++++++++++-------------------
1 file changed, 32 insertions(+), 19 deletions(-)
bisect found first bad commit
On Mon, Apr 21, 2025 at 12:08 PM Tom Gillespie <tgb...@gmail.com> wrote:
>
> Hi,
> I have found a bug where using #+call: on a block will fail to
> execute :file elisp, saving to the string rather than the evaluated
> result. It is on main at 9f3ee0fa5e3e8835dd34f134f05840aa28a21f5f.
> It is present in org 9.4.4 that comes with Emacs 27.2, but it is NOT
> present in org 9.1.9 that comes with Emacs 26.3, so the bug was
> introduced some time between 9.1.9 and 9.4.4. An example with the
> repro is below. Best,
> Tom
>
> #+begin_src org :tangle ./org/bug-call-ff-el.org
> ,#+name: should-save-to-oops.ext
> ,#+begin_src elisp :results file :file (or "oops.ext")
> 'hello
> ,#+end_src
>
> ,#+RESULTS: should-save-to-oops.ext
> [[file:oops.ext]]
>
> ,#+call: should-save-to-oops.ext()
>
> ,#+RESULTS:
> [[file:(or "oops.ext")]]
> #+end_src
