From: Ihor Radchenko <yantar92@posteo.net>
To: William Denton <wtd@pobox.com>, Jeremie Juste <jeremiejuste@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Seeing all the steps when I run an R code block
Date: Wed, 23 Nov 2022 11:15:42 +0000 [thread overview]
Message-ID: <87bkoxj50h.fsf@localhost> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2211221555120.61289@shell3.miskatonic.org>
William Denton <wtd@pobox.com> writes:
>> You might have set some customization that overrides `default-directory'
>> setting in ESS.
>
> You were quite right---thanks for checking. Recently ESS changed
> ess-startup-directory and now it's aware of projects. I'd recently put some
> files under Git, which made them a project. So it was ESS, nor R.
>
> For the record, this will stop that:
>
> (setq ess-startup-directory 'default-directory) ;; "Always start the process in the directory of the current file"
>
> But I have another R problem that does seem to be with Org, coming next ...
I think this specific issue might be solved on Org side.
We can let-bind `ess-startup-directory' to 'default-directory while
running R source blocks.
CCing the maintainer.
Jeremie, what do you think?
--
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-23 11:16 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 [this message]
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=87bkoxj50h.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).