emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: William Denton <wtd@pobox.com>
To: emacs-orgmode@gnu.org
Subject: Seeing all the steps when I run an R code block
Date: Sun, 13 Nov 2022 22:20:40 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2211132209230.150678@shell3.miskatonic.org> (raw)

I've got a few problems with R source blocks that I can't figure out.  They 
started late last month, I think.  I'm running Emacs and Org from the 
development trees, refreshing and recompiling regularly.  ESS (the package for 
working with R) is up to date too.

Here's one big problem.  I have a file, /home/wtd/books/reading/test-r.org, and 
in it is this R block:

# -----

#+begin_src R :session R:testing :results value
1
#+end_src

# -----

If I execute that with C-c C-c, the R session buffer starts, but in the wrong 
working directory.  This is in the R session buffer, reported by ESS:

# -----

> setwd('/home/wtd/books')

# -----

It's in the directory *above* where the Org file is!  It should be in 
/home/wtd/books/reading/.

I copied the test file to /tmp/r/test/, and it's fine there.  The session's 
working directory is /tmp/r/test/, not /tmp/r/.

Something strange is going on, but I can't see why.  Is there some way I can 
see all the steps that are happening when I hit C-c C-c on that code block?  Or 
maybe there's some other way to figure it out?  Any suggestions welcome.

Thanks,

Bill

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada

next             reply	other threads:[~2022-11-15  1:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  3:20 William Denton [this message]
2022-11-15  2:07 ` Seeing all the steps when I run an R code block 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
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=alpine.DEB.2.22.394.2211132209230.150678@shell3.miskatonic.org \
    --to=wtd@pobox.com \
    --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

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