From: Christian Heinrich <firstname.lastname@example.org>
To: emacs-orgmode <email@example.com>
Cc: Jeremie Juste <firstname.lastname@example.org>
Subject: Bug: ob-R.el breaks when :session is specified
Date: Sun, 15 May 2022 08:00:57 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
I got back to an org file after upgrading to the latest release of org-mode and tried executing the
contained R source blocks. Unfortunately, emacs got stuck in the execution and was blocked; I had to
exit using C-g.
Here's a minimal example src block that causes emacs to get stuck:
#+begin_src R :results output :session *R* :exports both
a <- 10
R itself does start and the code is also executed correctly. However, the output from that session
is apparently not returned to emacs or the buffer.
When removing the :session argument it executes and returns as expected.
When bisecting this issue, I found that this commit causes it:
lisp/ob-R.el: Fix session output with substrings matching prompts
Reverting it fixes the issue for earlier release (9.5.3) as well as for the current main branch.
The (with-current-buffer session ... ) somehow seems to break it for me, but I am unsure why no one
else here seems to experience this as the commit is from 2020?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-05-15 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 6:00 Christian Heinrich [this message]
2022-05-15 8:08 ` Bug: ob-R.el breaks when :session is specified Ihor Radchenko
2022-05-15 9:46 ` Christian Heinrich
2022-05-15 19:58 ` Berry, Charles
2022-05-16 5:26 ` Christian Heinrich
2022-05-15 14:16 ` Jeremie Juste
2022-05-15 18:06 ` Christian Heinrich
2022-05-15 22:21 ` Jeremie Juste
2022-05-16 5:23 ` Christian Heinrich
2022-05-16 5:24 ` Christian Heinrich
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).