From: John Hendy <jw.hendy@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 14:52:24 -0500 [thread overview]
Message-ID: <CA+M2ft_qYtBH3QvfQ_XSsYhqpoM-A2ZhRnKJ_E602KkuN87QiA@mail.gmail.com> (raw)
In-Reply-To: <829AC437-872D-453D-8543-B3C147F08B54@agrarianresearch.org>
On Sun, Jul 2, 2017 at 7:17 PM, 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.
As a frequent R user, I completely relate to this. As soon as one
evaluates code in the session buffer (C-c ') with C-RET, this is the
setup you get.
I'd add to your wish that upon first visiting a file, if I go into
edit mode, I'd like Org to pick up the fact that there's a :session
argument with a custom name and use that for C-RET in the edit buffer;
otherwise it generates the default *R* session there, but if you C-c
C-c the block later it puts it into the custom session name. Perhaps
out of habit, I tend to use :session r for every block that needs to
share results. I'll make some progress, close shop for the day, and to
continue where I left off I need to be sure to C-c C-c something the
next time rather than jumping right to editing. If I forget, end up
with two buffers and I get asked where I want to evaluate every
subsequent bit of code.
Anyway, it's easy enough to run one line with C-RET once editing and
get the session buffer, but just getting it right away is also what I
would prefer.
For other languages, even though one can't evaluate in the edit
buffer, I still use this view more frequently because I get
auto-indenting vs. none (e.g. with python).
John
>
>
> Vikas
next prev parent reply other threads:[~2017-07-03 19:52 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
2017-07-03 2:35 ` Andreas Kiermeier
2017-07-03 19:52 ` John Hendy [this message]
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=CA+M2ft_qYtBH3QvfQ_XSsYhqpoM-A2ZhRnKJ_E602KkuN87QiA@mail.gmail.com \
--to=jw.hendy@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).