emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Sam Crawford <sam@crawf.uk>
Cc: emacs-orgmode@gnu.org
Subject: [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)])
Date: Thu, 27 Jun 2024 09:41:51 +0000	[thread overview]
Message-ID: <871q4izpr4.fsf@localhost> (raw)
In-Reply-To: <Eol9qrqro63gxtIvCHknY775AV2QB4sVptOEZY__3tyWRRgw7GkCfbxqahcbQoVgNoQeqJzzXs5fHS-7ocn3OqTE0hJSwW9HCmWF4lt6N6g=@crawf.uk>

[ Adding Org mailing list back to CC to keep the conversation public ]

Sam Crawford <sam@crawf.uk> writes:

>>  May you please create a reproducer?
> Sure: evaluating the following code cell
> #+begin_src R :session R :async yes :results file graphics :file test.png
>   plot(iris$Sepal.Length, iris$Sepal.Width)
> #+end_src
> will call run-ess-r, which gives a prompt asking for the "R starting directory". Selecting any directory other than the directory the org file is located in will cause the issue.

I can reproduce, but I am not sure if this is something we are supposed
to fix.

The Org mode manual says the following about :dir header argument in
code blocks:

    The ‘dir’ header argument specifies the default directory during code
    block execution.  If it is absent, then the directory associated with
    the current buffer is used.
       When ‘dir’ is used with ‘session’, Org sets the starting directory
    for a new session.  But Org does not alter the directory of an already
    existing session.

ob-R currently does not obey what the manual says, and, when :dir is
omitted, allows the session directory to be set via prompt rather than
keeping the Org buffer's directory.

I'd like to hear from ob-R/ob-julia users whether the current behavior
is something they rely on. If not, I'd prefer to follow the conventions
we introduce in the manual and suppress the ESS's directory prompt.

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  parent reply	other threads:[~2024-06-27  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 10:57 [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)] Sam Crawford
2024-06-26 13:23 ` Ihor Radchenko
     [not found]   ` <Eol9qrqro63gxtIvCHknY775AV2QB4sVptOEZY__3tyWRRgw7GkCfbxqahcbQoVgNoQeqJzzXs5fHS-7ocn3OqTE0hJSwW9HCmWF4lt6N6g=@crawf.uk>
2024-06-27  9:41     ` Ihor Radchenko [this message]
2024-06-28 12:47       ` [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)]) 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:

  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=871q4izpr4.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=sam@crawf.uk \


* 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


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).