emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeremie Juste <jeremiejuste@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
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 17:02:36 +0100	[thread overview]
Message-ID: <871qpol71f.fsf@gmail.com> (raw)
In-Reply-To: <87cz98ipgx.fsf@localhost> (Ihor Radchenko's message of "Sun, 27 Nov 2022 11:52:46 +0000")

Hello Ihor,

On Sunday, 27 Nov 2022 at 11:52, Ihor Radchenko wrote:>

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

This is a fair point, many thanks the insights.

ESS indeed overrides the working directory when ess-startup-directory is
set to nil. It only happens when :sessions are used though. Here I
created created a git repository in /tmp/test, and when a process is
initiated with session (the last code chunk) the process is started in
at the root of the git repository. 

#+BEGIN_SRC elisp
  (setq ess-startup-directory nil)
#+END_SRC

#+BEGIN_SRC elisp
  default-directory
#+END_SRC

#+RESULTS:
: /tmp/test/books/reading/


#+BEGIN_SRC R
    getwd()
#+END_SRC

#+RESULTS:
: /tmp/test/books/reading


#+begin_src R :session R:testing :results value
getwd()
#+end_src

#+RESULTS:
: /tmp/test

Thanks again, I'll improve this.

Best regards,
Jeremie


      reply	other threads:[~2022-11-27 16:03 UTC|newest]

Thread overview: 7+ 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
2022-11-27 16:02           ` Jeremie Juste [this message]

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=871qpol71f.fsf@gmail.com \
    --to=jeremiejuste@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wtd@pobox.com \
    --cc=yantar92@posteo.net \
    /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).