emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug: ob-R.el breaks when :session is specified


From: Jeremie Juste
Subject: Re: Bug: ob-R.el breaks when :session is specified
Date: Mon, 16 May 2022 00:21:08 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

Hello Christian

On Sunday, 15 May 2022 at 20:06, Christian Heinrich wrote:
> I just tested with
>
>  Org mode version 9.5.3 (release_9.5.3-504-gcdbb1c @
> /home/heinrich/.emacs.d/straight/repos/org/lisp/)
>
> using
>
> GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.30, cairo 
> version 1.16.0) of 2021-
> 11-27, modified by Debian


Many thanks for reporting back.  I updated to gcdbb1c and it is still working 
fine.

My minimum working example is the following. From the org-mode root directory,

$ emacs -Q -L ./lisp -l org  -l ~/ess-barebone.el

where ~/ess-barebone.el is the following:

#+begin_src  elisp
(add-to-list 'load-path "/home/djj/.emacs.d/elpa/ess-20220125.2207/")
(require 'ess-r-mode)

 (org-babel-do-load-languages
   'org-babel-load-languages
   '((R . t)))

(setq org-confirm-babel-evaluate nil)
#+end_src

Note that I'm still using a rather old ess version. Could you please try
with the above configuration? Note that I am using a rather old ess
version but the I haven't experienced issues with the newer one.

Best regards
Jeremie


> Hi Jeremie,
>
> I just tested with
>
>  Org mode version 9.5.3 (release_9.5.3-504-gcdbb1c @
> /home/heinrich/.emacs.d/straight/repos/org/lisp/)
>
> using
>
> GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.30, cairo 
> version 1.16.0) of 2021-
> 11-27, modified by Debian
>
> I am on Debian Testing and that is the default emacs version.
>
> Using the unmodified org (git hash from above) I get the following messages 
> when executing a src
> block with R:
>
>    executing R code block...
>    Loading ‘ess-bugs-l’: unescaped character literals `?(', `?)' detected, 
> `?\(', `?\)' expected!
>    Type C-h m for help on ESS version 15.09
>    ess-tracebug mode enabled
>    Quit
>    Package cl is deprecated
>
> Note that the "Quit" is me pressing Ctrl-g after a few seconds.
>
> Removing the commit in question makes the block return instantaneously:
>
>    executing R code block...
>    Loading ‘ess-bugs-l’: unescaped character literals `?(', `?)' detected, 
> `?\(', `?\)' expected!
>    Type C-h m for help on ESS version 15.09
>    ess-tracebug mode enabled
>    Code block evaluation complete.
>    Package cl is deprecated
>
> I anticipated that this would not be obvious, since this feature is used too 
> much to go unnoticed for
> two years - but I am clueless as to how I should continue with debugging...
>
> Thanks for your help!
> Christian
>
> On Sun, 2022-05-15 at 16:16 +0200, Jeremie Juste wrote:
>> 
>> Hello Christian,
>> 
>> 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 @
>> /home/djj/src/org-mode/lisp/)
>> GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24) of
>> 2022-01-16
>> 
>> Can you please let me know which version of org-mode you are actually
>> using?
>> 
>> Ihor, many thanks for checking.
>> 
>> Best regards,
>> Jeremie
>> 
>> On Sunday, 15 May 2022 at 16:08, 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]