From: Jeremie Juste <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Cc: Christian Heinrich <firstname.lastname@example.org>,
Subject: Re: Bug: ob-R.el breaks when :session is specified
Date: Sun, 15 May 2022 16:16:31 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <877d6n2p6t.fsf@localhost> (Ihor Radchenko's message of "Sun, 15 May 2022 16:08:26 +0800")
Thanks for reporting but I cannot reproduce the bug with the org and
emacs version below.
Org mode version 9.5.3 (release_9.5.3-467-g2bd34e @
GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24) of
Can you please let me know which version of org-mode you are actually
Ihor, many thanks for checking.
On Sunday, 15 May 2022 at 16:08, Ihor Radchenko wrote:
> Christian Heinrich <firstname.lastname@example.org> writes:
>> 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.
> I tried you example using Emacs >=26 and it works just fine.
next prev parent reply other threads:[~2022-05-15 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 6:00 Bug: ob-R.el breaks when :session is specified Christian Heinrich
2022-05-15 8:08 ` 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 [this message]
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).