emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dylan Schwilk <dylan@schwilk.org>
To: "Berry\, Charles" <ccberry@health.ucsd.edu>
Cc: Jack Kamm <jackkamm@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Help debugging R source code block output problem with :session
Date: Sat, 29 Aug 2020 23:37:11 -0500	[thread overview]
Message-ID: <87d038agw8.fsf@havana> (raw)
In-Reply-To: <352C7149-743F-4944-ACA5-7A1242B5A3AA@health.ucsd.edu>

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:35, Berry, Charles 
<ccberry@health.ucsd.edu> wrote:

> This problem has been bugging people for years and previous 
> attempts to solve it have always run up against creating more 
> problems in the process of solving this one.
>
> This workaround gives the same results with or without `:session 
> "NEW"' and same as OPs first src block:
>
> #+header: :prologue "capture.output({" :epilogue "})"
> #+begin_src R :results value verbatim :session "NEW" 
> print("<X> <Y> <!>")
> print("one <two> three")
> print("end")
> #+end_src
>
> If you do decide to dig into solving this, please be sure that 
> remote sessions and graphical outputs are not broken. 
> test-ob-R.el does not cover those cases.  In fact, it is pretty 
> short, so there are probably other things that could break 
> without `make test' complaining.
>
> HTH,
>
> Chuck
>
>
>> On Aug 29, 2020, at 12:24 AM, Jack Kamm <jackkamm@gmail.com> 
>> wrote:
>> 
>> Hi Dylan,
>> 
>>> 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.
>> 
>> Of course, you're right. Good catch.
>> 
>> Here's another attempt. It fixes the issue by modifying the R 
>> comint
>> regular expression, requiring it to match at the beginning of 
>> the line.


-- 


  reply	other threads:[~2020-08-30  4:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 20:11 Dylan Schwilk
2020-08-29  2:36 ` Jack Kamm
2020-08-29  4:07   ` Dylan Schwilk
2020-08-29  7:24     ` Jack Kamm
2020-08-29 20:35       ` Berry, Charles via General discussions about Org-mode.
2020-08-30  4:37         ` Dylan Schwilk [this message]
2020-08-30 15:08         ` Jack Kamm
2020-09-07  8:18         ` Jack Kamm
2020-09-07  8:45           ` Jack Kamm
2020-09-07 17:37             ` Berry, Charles via General discussions about Org-mode.
2020-09-07 20:07               ` Jack Kamm
2020-09-07 22:12                 ` Berry, Charles via General discussions about Org-mode.
2020-09-08  1:06                   ` Jack Kamm
2020-09-08  2:08                     ` Berry, Charles via General discussions about Org-mode.
2020-09-08 14:51                       ` Jack Kamm
2020-09-08 16:45                         ` Berry, Charles via General discussions about Org-mode.
2020-09-08 17:41                           ` Jack Kamm
2020-09-18 16:39                             ` Dylan Schwilk
2020-10-28 13:13                 ` Jack Kamm
2020-10-28 13:46                   ` Jeremie Juste
2020-08-30  4:18       ` Dylan Schwilk
2021-05-03  8:53       ` Jeremie Juste

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=87d038agw8.fsf@havana \
    --to=dylan@schwilk.org \
    --cc=ccberry@health.ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=jackkamm@gmail.com \
    --subject='Re: Help debugging R source code block output problem with :session' \
    /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

Code repositories for project(s) associated with this 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).