emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Denton <william@williamdenton.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Seeing all the steps when I run an R code block
Date: Tue, 09 Apr 2024 23:49:14 +0000	[thread overview]
Message-ID: <LNHjY0VGVo-rdIf8bz0IKvwEsAMdezNhyaDqZlGtAd3UgX1D_oWk2fYb32oAQ84EslktHeD1ehrmvb2GYeMIn3pVaZN3UIKqE_Gd0DYOACs=@williamdenton.org> (raw)
In-Reply-To: <87ttkar8mp.fsf@localhost>

On Tuesday, April 9th, 2024 at 09:03, Ihor Radchenko <yantar92@posteo.net> wrote:

> > 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')
> 
> 
> I just tested with the latest version of ESS and I am no longer able to
> reproduce the problem.
> 
> Do you still see it on your side?

Thanks for following up.  No, I don't see it any more ... an ESS upgrade or something fixed the problem.

Bill

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




  reply	other threads:[~2024-04-09 23:50 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
2022-11-27 16:02           ` Jeremie Juste
2024-04-09 13:03 ` Ihor Radchenko
2024-04-09 23:49   ` William Denton [this message]
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='LNHjY0VGVo-rdIf8bz0IKvwEsAMdezNhyaDqZlGtAd3UgX1D_oWk2fYb32oAQ84EslktHeD1ehrmvb2GYeMIn3pVaZN3UIKqE_Gd0DYOACs=@williamdenton.org' \
    --to=william@williamdenton.org \
    --cc=emacs-orgmode@gnu.org \
    --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).