emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: Andreas Kiermeier <andreas.kiermeier@gmail.com>
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 07:58:15 +0530	[thread overview]
Message-ID: <ED295FEA-523D-4461-AB62-D31B6EA67808@agrarianresearch.org> (raw)
In-Reply-To: <CAN7vk5QNT-5CEiHpQPgoFo9X+CJCvHYpk-NEEps0F9fybh2BQQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

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

Thanks Andreas. I am perhaps being to finicky. The problem with your approach is that you would end up permanently losing screen space for the R session. I don’t want the R session obstructing my writing when I am not working on code blocks. Ideally, the R session should appear only when I am editing the code blocks in an edit buffer.

Vikas


[-- Attachment #2: Type: text/html, Size: 1919 bytes --]

  reply	other threads:[~2017-07-03  2:28 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
2017-07-03  2:28           ` Vikas Rawal [this message]
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=ED295FEA-523D-4461-AB62-D31B6EA67808@agrarianresearch.org \
    --to=vikaslists@agrarianresearch.org \
    --cc=andreas.kiermeier@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).