From: Ihor Radchenko <yantar92@posteo.net>
To: Jeremie Juste <jeremiejuste@gmail.com>
Cc: William Denton <wtd@pobox.com>, emacs-orgmode@gnu.org
Subject: Re: Seeing all the steps when I run an R code block
Date: Sun, 27 Nov 2022 11:52:46 +0000 [thread overview]
Message-ID: <87cz98ipgx.fsf@localhost> (raw)
In-Reply-To: <87mt8cy6ct.fsf@gmail.com>
Jeremie Juste <jeremiejuste@gmail.com> writes:
> Note also that you can force the R process to start in a particular
> directory with the dir parameter.
>
> #+begin_src R :dir ~/
> getwd()
> #+end_src
>
> #+RESULTS:
> : /home/djj
>
>
> Now on the org-mode side. This is becomes tricky because I don't know
> what users expects. For now this issue is delegated to the ESS configuration.
> Is the present state a satisfactory one? Please voice out your opinion.
From Org perspective, we should follow what :dir does and fallback to
buffer's `default-directory' otherwise:
16.4 Environment of a Code Block
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. In other words, supplying ‘:dir DIRECTORY’
temporarily has the same effect as changing the current directory with
‘M-x cd <RET> DIRECTORY’, and then not setting ‘dir’. Under the
surface, ‘dir’ simply sets the value of the Emacs variable
‘default-directory’. Setting ‘mkdirp’ header argument to a non-‘nil’
value creates the directory, if necessary.
For example, to save the plot file in the ‘Work/’ folder of the home
directory—notice tilde is expanded:
#+BEGIN_SRC R :file myplot.png :dir ~/Work
matplot(matrix(rnorm(100), 10), type="l")
#+END_SRC
So, if R has some way to override the working directory, we should
enforce what we promise in the above section of our manual anyway.
Otherwise, the will lose on Org document reproducibility.
--
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>
next prev parent reply other threads:[~2022-11-27 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 3:20 Seeing all the steps when I run an R code block William Denton
2022-11-15 2:07 ` Ihor Radchenko
2022-11-22 20:58 ` William Denton
2022-11-23 11:15 ` Ihor Radchenko
2022-11-27 11:38 ` Jeremie Juste
2022-11-27 11:52 ` Ihor Radchenko [this message]
2022-11-27 16:02 ` Jeremie Juste
2024-04-09 13:03 ` Ihor Radchenko
2024-04-09 23:49 ` William Denton
2024-04-10 12:48 ` Ihor Radchenko
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=87cz98ipgx.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jeremiejuste@gmail.com \
--cc=wtd@pobox.com \
/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).