From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frederick Giasson Subject: Re: [PATCH] new :async feature for org-babel-clojure Date: Wed, 27 Apr 2016 08:00:37 -0400 Message-ID: <9479db14-ec40-6d1b-605a-da757b01ec50@fgiasson.com> References: <56FABD8E.2000705@fgiasson.com> <87twjfcbt6.fsf@nicolasgoaziou.fr> <570538F9.8030307@fgiasson.com> <87a8kohrgi.fsf@nicolasgoaziou.fr> <0bf9b99d-139f-b54d-f3b5-e5e1f1344e4b@fgiasson.com> <87h9eomb14.fsf@saiph.selenimh> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52508) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avO96-00040b-LC for emacs-orgmode@gnu.org; Wed, 27 Apr 2016 08:00:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1avO92-0002uh-34 for emacs-orgmode@gnu.org; Wed, 27 Apr 2016 08:00:44 -0400 Received: from s052.panelboxmanager.com ([72.55.186.33]:44662) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1avO91-0002uL-Vs for emacs-orgmode@gnu.org; Wed, 27 Apr 2016 08:00:40 -0400 Received: from mailnull by s052.panelboxmanager.com with sa-checked (Exim 4.86_1) (envelope-from ) id 1avO8y-000TaV-Ri for emacs-orgmode@gnu.org; Wed, 27 Apr 2016 08:00:36 -0400 Received: from modemcable161.56-23-96.mc.videotron.ca ([96.23.56.161]:59416 helo=[192.168.0.13]) by s052.panelboxmanager.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86_1) (envelope-from ) id 1avO8y-000Ta4-Gs for emacs-orgmode@gnu.org; Wed, 27 Apr 2016 08:00:36 -0400 In-Reply-To: <87h9eomb14.fsf@saiph.selenimh> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org 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, > etc.). 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. Thoughts? Thanks, Fred > > > Regards, >