Re: [O] change in calling remote code blocks?

[John Kitchin]

I don't recall how I learned about that, I guess maybe in some library of babel documentation somewhere. I confirmed it does work in 8.2.10, e.g. just with emacs -Q.

There are a few changes in org 9 to org-babel-lob-execute-maybe and org-babel-lob-get-info that seem to be the root cause of the change. Notably, org-babel-lob-get-info now returns nil where it used to return the "path" to the file and block.

So, if I put this into an org file

(progn

 (re-search-forward "call")

 (message "%s" (org-babel-lob-get-info)))   ;<- execute here

#+call: remote-call.org:test-block()

These get returned

In 8.2.10: "(remote-call.org:test-block() nil 0 nil)"

In 9.1.6: "nil"

I am not sure what all the differences are, but it seems to be where the change in behavior came from.

John

-----------------------------------
Professor John Kitchin 
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803

@johnkitchin
http://kitchingroup.cheme.cmu.edu

On Mon, Jan 15, 2018 at 2:49 PM, Nicolas Goaziou <address@hidden> wrote:

Hello,

John Kitchin <address@hidden> writes:

> In org8 I used to be able to call remote code blocks (
> http://kitchingroup.cheme.cmu.edu/blog/2016/02/09/Calling-remote-code-blocks-in-org-mode/
> )
>
> with a syntax like:
>
> #+call: si.org:figure-1() :wrap html
>
> And C-c C-c on that line would call a code block named figure-1 in the file
> si.org and insert the results.
>
> in org 9.1.6, this does nothing. Does anyone know if this got changed, and
> if there is a new way to do that?

This sounds like a bug.

It does ring a bell. However, I couldn't find any reference to this
syntax or behaviour in the manual. Am I missing something?

Regards,

--
Nicolas Goaziou