Thanks. This patch works for my org files.
On Tue 08 Sep 2020 at 12:41, Jack Kamm wrote:
Hi Chuck,
this is already present in `org-babel-R-evaluate-session' in
the call to
`org-babel-comint-eval-invisibly-and-wait-for-file'' just a
couple of lines further down in the `(cl-case result-type
Thanks for the workaround idea of grabbing the results as a
string.
I'm not sure why this issue cropped up for me right now when I did
not run into it in previous years. But I have run into other
:results output issues in the past when ess changed.
Thanks,
Dylan
On Sat 29 Aug 2020 at 15:3
Yes, the modified comint-prompt-regexp works for my use cases and
I'm back to expected output and what I had last time I taught the
course. This was my instinct for a simple solution as well, but
I've not tested against remote sessions and graphical outputs as
Charles Berry warns.
I'll take a
Hi Jack,
The patch does fix that issue -- but it introduces a different bug
for code blocks with ~:session~: the R block now only produces
output from the last statement evaluated.
#+begin_src R :results output :exports both :session
4.0 * 3.5
log(10) # natural log
log10(10)
(3 + 1) * 5
3^-1
I returned to an org file this week and found that I am getting
some strange source code block output for R code when I use the
:session header. I have been able to duplicate this with a minimal
init file. I strongly suspect it is some problem at my end but
perhaps folks here can help me know h
ands, but don’t wait for the process.).
My apologies for the spurious post. I had not realized that I was setting that
ess variable.
Sincerely,
Dylan
On 08/28/2018 11:57 AM, Berry, Charles wrote:
> Cannot confirm. See inline.
>
>> On Aug 28, 2018, at 7:48 AM, Dylan Schwilk wrote:
&g
Hello,
I recently have run into a change in output from my R language source code
blocks.
I have found that when I include :session to the source block header, I now get
extra blank lines in the #+results. This has broken my lecture slides for my
courses with too much extra blank space.
for exa
this particular case regardless of the
value of org-yank-adjusted-subtrees?
- Dylan Schwilk
On Tue, Aug 5, 2014 at 1:00 PM, Ken Mankoff wrote:
> Yes that works perfectly. Not sure why I had memorized a different
> keystroke. Thank you!
>
>
>
> On Tue, Aug 5, 2014 at 1:46 P
