[Top][All Lists]

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

Re: [O] [PATCH] new :async feature for org-babel-clojure

From: Frederick Giasson
Subject: Re: [O] [PATCH] new :async feature for org-babel-clojure
Date: Wed, 27 Apr 2016 08:00:37 -0400
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0

Hi Nicolas,

Right now, async is really more about "feedback" than "asynchronous".
However it has never been clear is it was possible or not, and if so,
how :)

Any pointers on how this could be done in emacs?
You could start a new Emacs evaluating some code in a subprocess, with
`start-process' and collect return value. You may want to have a look at
`org-export-async-start' or "async.el" library in ELPA.

Unfortunately, it is not yet possible to re-use the latter in Org code,
since it is unavailable in vanilla Emacs.

The hard part, IMO, is to bring the right context in the subprocess
(e.g., the environment should be the same, other blocks may be needed,

Yeah, will have to take some more time to check that, I probably have much to learn regarding Elisp itself first.

Rethinking about that, would it not be better to remove the confusion by changing the terminology I used: ":async"? What it really is is to have feedback of the underlying process, and not really an asynchronous process.

I thought about two possibilities:

(1) creating two new results options: :output-process and :value-process. Which means that we output the underlying process of a :output or :value :results
  (2) renaming :async by :show-process or something similar.

Then we take the time to check how a real asynchronous system can be put in place.





reply via email to

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