From: Jack Kamm <jackkamm@gmail.com>
To: Jeremie Juste <jeremiejuste@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-babel strange html print in R
Date: Fri, 07 Feb 2020 17:30:37 -0800 [thread overview]
Message-ID: <874kw1uapu.fsf@gmail.com> (raw)
In-Reply-To: <87pneqnecb.fsf@gmail.com>
Hi Jeremie,
> Thanks for the info.
> Unfortunately I couldn't identify the issue
> I updated R and org (org 9.3.2, R 3.6.2).
> but I'm still getting [the error]
Sorry, I missed the initial property line where you set the ":session"
header argument.
When I set the ":session" header argument, I get the original buggy
behavior that you report.
It looks like the reason for this, is that the substrings like "tr>"
match `comint-prompt-regexp', and so get stripped out by
`org-babel-comint-with-output'.
I think a more reliable implementation would be to avoid
`org-babel-comint-with-output', and take the approach used in the
":results value" case, which reads the output from a temp file instead
of directly from the shell.
Actually, that's the approach I use in my ob-session-async package [0],
which re-implements ob-R sessions to allow async evaluation. It doesn't
suffer from the bug you are reporting. I'll plan to extract that
implementation and submit it as a patch here.
Long term, I am intending to contribute the full functionality in
ob-session-async here, but that's still a ways off.
[0] https://github.com/jackkamm/ob-session-async
Jack
next prev parent reply other threads:[~2020-02-08 1:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 18:23 org-babel strange html print in R Jeremie Juste
2020-02-07 12:53 ` Dominique Dumont
2020-02-07 13:38 ` Bastien
2020-02-07 15:23 ` Dominique Dumont
2020-02-07 14:51 ` Jack Kamm
2020-02-07 23:54 ` Jeremie Juste
2020-02-08 1:30 ` Jack Kamm [this message]
2020-02-08 8:42 ` Jeremie Juste
2020-02-11 5:16 ` stardiviner
2020-02-11 15:40 ` Jack Kamm
2020-02-11 17:30 ` Jeremie Juste
2020-02-11 23:25 ` Jack Kamm
2020-02-12 7:05 ` stardiviner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kw1uapu.fsf@gmail.com \
--to=jackkamm@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jeremiejuste@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.