Support running blocks sequentially with org-babel-execute-subtree about ob-async HOT 3 OPEN

Off the top of my head, we might be able to add a new function like ob-async-execute-subtree which adds a function to org-babel-after-execute-hook and kicks off the first src-block. The hook function would then jump to the next src-block and execute it.

Open to ideas or pull requests, here.

from ob-async.

Without async mode, you could achieve something like this by defining blocks as inputs of other blocks, e.g.:

* Test

#+begin_src emacs-lisp :results none
(setq-local org-confirm-babel-evaluate nil)
#+end_src

#+name: test1
#+begin_src sh :results verbatim :cache yes
sleep 3
echo test 1
date -u
#+end_src

#+begin_src sh :results verbatim :var ignore=test1 :cache yes
date -u
echo test 2
#+end_src

The second block will wait for the first block to complete, perhaps implicitly because evaluation is blocking (I don't know) but the effect is the same: this works.

With ob-async, it seems like a block is immediately considered "done" from babel's pov, so the next block will start immediately, with the first (place-holder) result as input. An error is thrown and the second block never completes:

error in process sentinel: if: Invalid read syntax: "#<"
error in process sentinel: Invalid read syntax: "#<"

If ob-async could somehow detect that an input block is, itself, a pending ob-async operation, and block evaluation until that dependent block is done, you could fix both the expected behaviour, and this github issue could be solved by using the same technique.

What do you think?

from ob-async.

Related to #60

from ob-async.