emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Heinrich <com-orgmode-mailinglist@gladbachcity.de>
To: Christian Heinrich <com-orgmode-mailinglist@gladbachcity.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: ob-R.el breaks when :session is specified
Date: Sun, 15 May 2022 11:46:52 +0200	[thread overview]
Message-ID: <00299684ab44443c1c5e8433dc251e48ba66594c.camel@gladbachcity.de> (raw)
In-Reply-To: <877d6n2p6t.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]


thanks, that's what I had expected since that patch has been around for a long time.

I run 

 emacs -q --load /tmp/init.el --file=/tmp/test.org 

with my /tmp/init.el being only

> (require 'package)
> (package-initialize)
> (add-to-list 'load-path "~/.emacs.d/straight/repos/org/lisp/")
> (require 'org)
> ;(require 'ess-site)
> (org-babel-do-load-languages
>    'org-babel-load-languages
>     '((R . t)))

I hope this constitutes a minimal example for a config - please correct me if I'm wrong.

My test.org contains the source block I had already posted:

#+begin_src R :results output :session *R* :exports both
  a <- 10

Any ideas how I could continue to debug this? If I just remove that patch, everything works
flawlessly for me but I would like to figure out what causes the issues.



On Sun, 2022-05-15 at 16:08 +0800, Ihor Radchenko wrote:
> Christian Heinrich <com-orgmode-mailinglist@gladbachcity.de> 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
> >   a
> > #+end_src
> > 
> > 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.
> Best,
> Ihor

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-05-15  9:47 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 [this message]
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

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:

  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=00299684ab44443c1c5e8433dc251e48ba66594c.camel@gladbachcity.de \
    --to=com-orgmode-mailinglist@gladbachcity.de \
    --cc=emacs-orgmode@gnu.org \


* 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).