Re: [O] org babel, ess, R

Hello, John Hendy writes: > Really, it was a comment about how Org behaves, not necessarily a bug. > That said, speaking for myself, I would never want a default session > in interactive mode when I've defined one in the code heading. I'd > love if Org could pick up on that

Re: [O] org babel, ess, R

On Wed, 5 Jul 2017, Vikas Rawal wrote: "... 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

Re: [O] org babel, ess, R

>> >> "... 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." > > This is what

Re: [O] org babel, ess, R

On Wed, 5 Jul 2017, John Hendy wrote: On Wed, Jul 5, 2017 at 4:22 PM, Nicolas Goaziou wrote: Hello, Vikas Rawal writes: C-RET seems to be picking up the custom session name if it is already there. But otherwise it generates the

Re: [O] org babel, ess, R

On Wed, Jul 5, 2017 at 4:22 PM, Nicolas Goaziou wrote: > Hello, > > Vikas Rawal writes: > >> C-RET seems to be picking up the custom session name if it is already >> there. But otherwise it generates the default *R* session there, > > Is

Re: [O] org babel, ess, R

Hello, Vikas Rawal writes: > C-RET seems to be picking up the custom session name if it is already > there. But otherwise it generates the default *R* session there, Is there a bug to fix? If so, could start a new thread about it, ideally with an ECM

Re: [O] org babel, ess, R

>> possibility of evaluating the code to test and see what happens? > > Often, but not always. And it would be seriously annoying to have the > session buffer pop up every time I wanted to browse the code in a src block > while simultaneously viewing the results of a previous invocation

Re: [O] org babel, ess, R

On Tue, 4 Jul 2017, Vikas Rawal wrote: On 04-Jul-2017, at 1:22 AM, John Hendy wrote: On Sun, Jul 2, 2017 at 7:17 PM, Vikas Rawal wrote: Vikas Rawal writes: Isn’t is what most users need while editing

Re: [O] org babel, ess, R

> On 04-Jul-2017, at 1:22 AM, John Hendy wrote: > > On Sun, Jul 2, 2017 at 7:17 PM, Vikas Rawal > wrote: >>> >>> Vikas Rawal writes: >>> Isn’t is what most users need while editing the code block? The

Re: [O] org babel, ess, R

On Sun, Jul 2, 2017 at 7:17 PM, Vikas Rawal wrote: >> >> Vikas Rawal 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

Re: [O] org babel, ess, R

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

Re: [O] org babel, ess, R

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

Re: [O] org babel, ess, R

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

Re: [O] org babel, ess, R

> > Vikas Rawal 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

Re: [O] org babel, ess, R

Hello, Vikas Rawal 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

Re: [O] org babel, ess, R

> >> When I press C-c' in an R code block to open an edit buffer with ess, on my >> computer, it splits the screen into two side-by-side windows, with the new >> window on the right showing the edit buffer, and the window on the left >> showing the original file. >> >> I would like to change

Re: [O] org babel, ess, R

Hello, Vikas Rawal writes: > When I press C-c' in an R code block to open an edit buffer with ess, on my > computer, it splits the screen into two side-by-side windows, with the new > window on the right showing the edit buffer, and the window on the left >

Re: [O] org babel, ess, R

> > When I press C-c' in an R code block to open an edit buffer with ess, on my > computer, it splits the screen into two side-by-side windows, with the new > window on the right showing the edit buffer, and the window on the left > showing the original file. > > I would like to change this

[O] org babel, ess, R

When I press C-c' in an R code block to open an edit buffer with ess, on my computer, it splits the screen into two side-by-side windows, with the new window on the right showing the edit buffer, and the window on the left showing the original file. I would like to change this behaviour in two