From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: pjb@informatimago.com (Pascal J. Bourguignon) Newsgroups: gmane.emacs.help Subject: Re: Asynchronous Process Handling Date: Fri, 26 Jun 2009 15:48:30 +0200 Organization: Anevia SAS Message-ID: <7cbpobkswh.fsf@pbourguignon.anevia.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1246028199 10576 80.91.229.12 (26 Jun 2009 14:56:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 26 Jun 2009 14:56:39 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jun 26 16:56:32 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MKCqf-000566-1E for geh-help-gnu-emacs@m.gmane.org; Fri, 26 Jun 2009 16:56:17 +0200 Original-Received: from localhost ([127.0.0.1]:40727 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MKCqe-0003Ip-CJ for geh-help-gnu-emacs@m.gmane.org; Fri, 26 Jun 2009 10:56:16 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.straub-nv.de!proxad.net!feeder1-2.proxad.net!cleanfeed1-a.proxad.net!nnrp7-1.free.fr!not-for-mail Original-Newsgroups: gnu.emacs.help Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en X-Disabled: X-No-Archive: no User-Agent: Gnus/5.101 (Gnus v5.10.10) Emacs/22.2 (gnu/linux) Cancel-Lock: sha1:AwlGv3jd9QgcjReWO6JmGkaKiB0= Original-Lines: 32 Original-NNTP-Posting-Date: 26 Jun 2009 15:48:31 MEST Original-NNTP-Posting-Host: 88.170.236.224 Original-X-Trace: 1246024111 news-2.free.fr 306 88.170.236.224:48657 Original-X-Complaints-To: abuse@proxad.net Original-Xref: news.stanford.edu gnu.emacs.help:170335 X-Mailman-Approved-At: Fri, 26 Jun 2009 10:52:19 -0400 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:65555 Archived-At: Nordlöw writes: > Is it possible to call a process asynchronously from with emacs and > later get back an async message or notification when the process has > finished possibly along with its return value and or output? Yes. You can do it with processes and process filters. I let you read the documentation about them. Here is another solution, which has the advantage for long processes, to work even if you relaunch emacs. Put: (defun process-my-result (result) (switch-to-buffer "*result*") (insert (format "%S" result))) (server-start) in ~/.emacs and launch the process as: (shell-command "( sleep 10 ; result=42 ; emacsclient --eval \"(process-my-result $result)\" ) & disown &" nil nil) -- __Pascal Bourguignon__