From: Andreas Kiermeier <andreas.kiermeier@gmail.com>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: org babel, ess, R
Date: Mon, 3 Jul 2017 11:51:43 +0930 [thread overview]
Message-ID: <CAN7vk5QNT-5CEiHpQPgoFo9X+CJCvHYpk-NEEps0F9fybh2BQQ@mail.gmail.com> (raw)
In-Reply-To: <829AC437-872D-453D-8543-B3C147F08B54@agrarianresearch.org>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
Hi Vikas,
for what it's worth, I usually run two windows (in the same frame),
side-by-side, with emacs maximised.
On the left I have my org file and on the right I have an R session, which
I start immediately after I open my org file.
When I use C-c ' on an R source block, the org buffer (on the left) is
replaced by by the source code edit buffer - leaving the R-session on the
right untouched.
That way I can either evaluate a whole code block (from org using C-c C-c)
or go through the source code line-by-line (using ESS).
Seems like that's what you want to do, too.
Anyway, just my two cents worth, in case it helps.
Cheers,
AK
On 3 July 2017 at 09:47, Vikas Rawal <vikaslists@agrarianresearch.org>
wrote:
> >
> > Vikas Rawal <vikaslists@agrarianresearch.org> writes:
> >
> >> Isn’t is what most users need while editing the code block? The
> >> possibility of evaluating the code to test and see what happens?
> >
> >
> > Many languages do not support sessions. So, the only possibility to
> > evaluate the code is to evaluate the code block in the source buffer.
> >
>
> Yes, what I am talking about is relevant only when a session is defined.
> What I would like is that if in a file the session is defined, C-c’ creates
> a window configuration that shows the edit buffer and the session. In
> other cases, the two windows could show the edit buffer and the original
> org buffer.
>
>
> Vikas
>
[-- Attachment #2: Type: text/html, Size: 2787 bytes --]
next prev parent reply other threads:[~2017-07-03 2:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 1:36 org babel, ess, R Vikas Rawal
2017-07-01 3:38 ` Vikas Rawal
2017-07-01 12:53 ` Nicolas Goaziou
2017-07-02 2:48 ` Vikas Rawal
2017-07-02 7:05 ` Nicolas Goaziou
2017-07-03 0:17 ` Vikas Rawal
2017-07-03 2:21 ` Andreas Kiermeier [this message]
2017-07-03 2:28 ` Vikas Rawal
2017-07-03 2:35 ` Andreas Kiermeier
2017-07-03 19:52 ` John Hendy
2017-07-03 23:19 ` Vikas Rawal
2017-07-04 2:17 ` Charles C. Berry
2017-07-04 9:20 ` Vikas Rawal
2017-07-05 21:22 ` Nicolas Goaziou
2017-07-05 21:58 ` John Hendy
2017-07-06 4:42 ` Charles C. Berry
2017-07-06 4:53 ` Vikas Rawal
2017-07-06 5:25 ` Charles C. Berry
2017-07-07 11:57 ` Nicolas Goaziou
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=CAN7vk5QNT-5CEiHpQPgoFo9X+CJCvHYpk-NEEps0F9fybh2BQQ@mail.gmail.com \
--to=andreas.kiermeier@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=vikaslists@agrarianresearch.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).