org-babel-execute-src-block on +#CALL statement?

org-babel-execute-src-block on +#CALL statement?

[Joon Ro]

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

Hi,

Eventually I would like to batch-run a src block in a command line. While investigating it, I found that org-babel-execute-src-block throws "Wrong type argument: consp, nil" error when I run it over a #+CALL statement. For example, I can run the test src block below but it fails when the cursor is on the #+CALL block.

#+NAME: test
#+BEGIN_SRC emacs-lisp
(message "Success")
#+END_SRC

#+RESULTS: test
: Success

#+CALL: test()


I was wondering if this is a bug, and if there is any way I can run #+CALL statement (preferably in the batch mode)?

Best,
Joon



[-- Attachment #2: Type: text/html, Size: 2052 bytes --]

Re: org-babel-execute-src-block on +#CALL statement?

[Nicolas Goaziou]

Hello,

Joon Ro <joon.ro@outlook.com> writes:
> Eventually I would like to batch-run a src block in a command line.
> While investigating it, I found that org-babel-execute-src-block
> throws "Wrong type argument: consp, nil" error when I run it over
> a #+CALL statement. For example, I can run the test src block below
> but it fails when the cursor is on the #+CALL block.
>
> #+NAME: test
> #+BEGIN_SRC emacs-lisp
>
> (message "Success") #+END_SRC
>
> #+RESULTS: test
> : Success
>
> #+CALL: test()
>
> I was wondering if this is a bug,

Why would this be a bug? `org-babel-execute-src-block' is meant to
execute source blocks. The Babel call line is not one of them. You need
to extract the source block associated to it, with
`org-babel-lob-get-info', and then pass it as an argument to
`org-babel-execute-src-block'.

> and if there is any way I can run #+CALL statement (preferably in the
> batch mode)?

I think the most straightforward way is to use `org-ctrl-c-ctrl-c'.

Regards,

-- 
Nicolas Goaziou