From: Sam Crawford <sam@crawf.uk>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)]
Date: Tue, 25 Jun 2024 10:57:11 +0000 [thread overview]
Message-ID: <16Z2_l6WnvrrYSQE7LC5XJQB3dO0DNAREBe7F4yE_DuNVOpHzqwELJ08ditlBSgFv_nnI3FSwi0JYCLEpd9CMqViJHxHiR3XbGeqDf4DM7Y=@crawf.uk> (raw)
When running an R session for org babel, if the working directory of
that session is different to the directory of the org file, then source
blocks with :results (output) graphics file will not work correctly. I
believe this is due to the fact that
org-babel-R-construct-graphics-device-call uses a relative filename.
I'm not sure what the best way to fix this is. My workaround was to
replace out-file with (file-name-concat default-directory out-file) in
the call to format at the end of
org-babel-R-construct-graphics-device-call, but I'm not convinced this
is the best way to do things.
Emacs : GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.42, cairo version 1.18.0)
of 2024-06-21
Package: Org mode version 9.8-pre (release_9.7.4-80-g7fa169 @ /var/home/sam/.emacs.d/straight/build/org/)
next reply other threads:[~2024-06-26 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 10:57 Sam Crawford [this message]
2024-06-26 13:23 ` [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)] Ihor Radchenko
[not found] ` <Eol9qrqro63gxtIvCHknY775AV2QB4sVptOEZY__3tyWRRgw7GkCfbxqahcbQoVgNoQeqJzzXs5fHS-7ocn3OqTE0hJSwW9HCmWF4lt6N6g=@crawf.uk>
2024-06-27 9:41 ` [POLL] ob-R, ob-julia: Should we force-disable ess-ask-for-ess-directory? (was: [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)]) Ihor Radchenko
2024-06-28 12:47 ` Rudolf Adamkovič
2024-06-28 13:46 ` Christian Moe
2024-06-28 15:09 ` [POLL] ob-R, ob-julia: Should we force-disable ess-ask-for-ess-directory? Suhail Singh
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='16Z2_l6WnvrrYSQE7LC5XJQB3dO0DNAREBe7F4yE_DuNVOpHzqwELJ08ditlBSgFv_nnI3FSwi0JYCLEpd9CMqViJHxHiR3XbGeqDf4DM7Y=@crawf.uk' \
--to=sam@crawf.uk \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).