From: Dylan Schwilk <dylan@schwilk.org>
To: emacs-orgmode@gnu.org
Subject: Help debugging R source code block output problem with :session
Date: Fri, 28 Aug 2020 15:11:55 -0500 [thread overview]
Message-ID: <87r1rqled0.fsf@havana> (raw)
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 here to look? It occurs with a
minimal emacs initialization.
First, here is a small org file example of the problem. In the
second results block the ">" appears to be treated as a prompt
line to strip from output but only when a session is started. This
happens with any ">" in output when the :session header occurs.
the problem is dramatic when printing tibbles where the column
modes are enclosed in angle brackets.
test.org
>>>
** Test org babel R output prompt problem
#+begin_src R :results output
print("<X> <Y> <!>")
print("one <two> three")
print("end")
#+end_src
#+RESULTS:
: [1] "<X> <Y> <!>"
: [1] "one <two> three"
: [1] "end"
#+begin_src R :results output :session "NEW"
print("<X> <Y> <!>")
print("one <two> three")
print("end")
#+end_src
#+RESULTS:
: [1] "<
: <
: <!>"
: [1] "one <
: three"
: [1] "end"
<<<
The second block produces the bad output. This occurs with a
minimal setup.
I start emacs with
> emacs -Q -l "~/debugorg.el"
where debugorg.el is:
>>
require 'package)
add-to-list 'package-archives '("melpa" .
"https://melpa.org/packages/") t)
add-to-list 'package-archives '("org" .
"https://orgmode.org/elpa/") t)
package-initialize)
require 'ess-site)
(org-babel-do-load-languages
'org-babel-load-languages
'((R . t)))
<<
emacs version 26.3
org-mode version 9.3.7
ess version 18.10.3snapshot
--
next reply other threads:[~2020-08-28 20:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 20:11 Dylan Schwilk [this message]
2020-08-29 2:36 ` Help debugging R source code block output problem with :session 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
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
-- strict thread matches above, loose matches on Subject: below --
2022-01-11 23:36 John Hendy
2022-01-12 7:49 ` Jeremie Juste
2022-01-12 15:04 ` John Hendy
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=87r1rqled0.fsf@havana \
--to=dylan@schwilk.org \
--cc=emacs-orgmode@gnu.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).