Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
This is a simplified reproducer of the problem, as discovered by user
@lyndhurst on SE Emacs. See
https://emacs.stackexchange.com/questions/82261/set-org-babel-source-block-parameters-dynamically
for more details.
Starting with `emacs -Q', open the following file:
--8<---------------cut here---------------start------------->8---
* Bug report example
#+begin_src shell
echo "foo"
#+end_src
* Code
#+begin_src elisp :results raw
(setq org-babel-default-header-args:shell '((:results . "file") (:file .
"results.txt") (:output-dir . "a")))
#+end_src
--8<---------------cut here---------------end--------------->8---
Evaluate the last code block to set
`org-babel-default-header-args:shell' to the indicated value, then
evaluate the shell code block repeatedly: the first time it works to
produce an output file `a/results.txt'; subsequent evaluations produce
errors:
org-ctrl-c-ctrl-c: Opening output file: No such file or directory,
.../a/a/results.txt
org-ctrl-c-ctrl-c: Opening output file: No such file or directory,
.../a/a/a/results.txt
org-ctrl-c-ctrl-c: Opening output file: No such file or directory,
.../a/a/a/a/results.txt
Note the increasing number of copies of the `output-dir' setting.
The value of `org-babel-default-header-args:shell' is modified every
time:
((:results . "file") (:file . "a/a/a/a/results.txt") (:output-dir . "a"))
The problem is the way that `org-babel-get-src-block-info' constructs
the `info' variable, which is used to pass around information during the
evaluation: the value depends on the `org-babel-default-header-args*'
variables, but is modified in place, and because of shared list
structure, the modification gets propagated to the user variables.
Emacs : GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.43,
cairo version 1.18.0) of 2024-08-09
Package: Org mode version 9.8-pre (release_9.7.10-127-g07dd3b
@/usr/local/share/emacs/site-lisp/org/)
------------------------------------------------------------------
The following patch wraps calls to `copy-tree' around the relevant
places to eliminate the sharing.
>From dfe13482a8b3997aaca35063e81c7535faf02c0b Mon Sep 17 00:00:00 2001
From: Nick Dokos <ndo...@gmail.com>
Date: Sat, 28 Sep 2024 15:39:25 -0400
Subject: [PATCH] org-babel: Avoid changing user options by not sharing list
structure
* lisp/ob-core.el (org-babel-get-src-block-info): Use `copy-tree'
when using `org-babel-default-header-args*' variables to prepare the
`info' variable used in src block evaluation. The `info' variable gets
modified, and the modifications were affecting the values of the user
variables. In particular, the `:file' setting was modified in the presence
of a `:output-dir' setting, concatenating more and more copies of the directory
every time the block was evaluated.
Reported-by: @lyndhurst on SE Emacs
Link: https://emacs.stackexchange.com/questions/82261/
---
lisp/ob-core.el | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index 90c52f8b7836..e6db422c9d20 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -731,9 +731,17 @@ Otherwise, return a list with the following pattern:
lang
(org-babel--normalize-body datum)
(apply #'org-babel-merge-params
- (if inline org-babel-default-inline-header-args
- org-babel-default-header-args)
- (and (boundp lang-headers) (eval lang-headers t))
+ ;; Use `copy-tree' to avoid creating shared structure
+ ;; with the `org-babel-default-header-args-*' variables:
+ ;; modifications by `org-babel-generate-file-param'
+ ;; below would modify the shared structure, thereby
+ ;; modifying the variables.
+ (copy-tree
+ (if inline org-babel-default-inline-header-args
+ org-babel-default-header-args)
+ t)
+ (and (boundp lang-headers)
+ (copy-tree (eval lang-headers t) t))
(append
;; If DATUM is provided, make sure we get node
;; properties applicable to its location within
--
2.46.0
--
Nick
