From: Daniele Pizzolli <dan@toel.it>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Evaluating R source code line by line
Date: Sat, 13 Dec 2014 11:12:05 +0100 [thread overview]
Message-ID: <86y4qbkgei.fsf@me.localhost.invalid> (raw)
In-Reply-To: <BF4BFF2D-4DE9-4A3D-A69D-BBD6976360C1@agrarianresearch.org> (Vikas Rawal's message of "Sat, 13 Dec 2014 07:56:44 +0530")
Hello,
Vikas Rawal writes:
> I have an R source code blocks called with the ":results value”
> option. I evaluate the code with C-c. When I do that, in my R session
> buffer, I get to see several + + + until the final value is obtained,
> and then the final value is shown, and inserted in my Org buffer.
>
> I was wondering if there is an option somewhere that will allow me to
> instead see how each line in my R source code is evaluated. That is,
> the R session buffer should show each line being evaluated, and then
> show the final value as usual.
Look at:
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
Use ESS to step through evaluation line-by-line
Use C-c ' to visit the edit buffer for your code block
Use ess-eval-line-and-step to evaluate each line in turn
ess-eval-line-and-step is usually bound to C-c C-n
I guess that is possible to use the same R session by configuring the
session arguments and/or the ESS settings but I have not done it yet.
If you do not have ESS you can try a more lightweight solution with
isend-mode.
Best,
Daniele
next prev parent reply other threads:[~2014-12-13 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 2:26 Evaluating R source code line by line Vikas Rawal
2014-12-13 10:12 ` Daniele Pizzolli [this message]
2014-12-13 13:18 ` Vikas Rawal
2014-12-13 19:38 ` Aaron Ecay
2014-12-15 22:58 ` Vikas Rawal
2014-12-16 16:32 ` Andreas Leha
2014-12-16 18:43 ` Andreas Leha
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=86y4qbkgei.fsf@me.localhost.invalid \
--to=dan@toel.it \
--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
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).