From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Barry Margolin Newsgroups: gmane.emacs.help Subject: Re: Call lisp function asynchronous Date: Sat, 09 Jun 2007 00:14:21 -0400 Organization: Symantec Message-ID: References: <87myzbktwu.fsf@lion.rapttech.com.au> NNTP-Posting-Host: lo.gmane.org X-Trace: sea.gmane.org 1181364152 15718 80.91.229.12 (9 Jun 2007 04:42:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 9 Jun 2007 04:42:32 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 09 06:42:31 2007 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 1HwsmS-00026f-Cw for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Jun 2007 06:42:28 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HwsmR-0000ej-UM for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Jun 2007 00:42:27 -0400 Original-Path: shelby.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!nx01.iad01.newshosting.com!newshosting.com!216.196.98.140.MISMATCH!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail Original-NNTP-Posting-Date: Fri, 08 Jun 2007 23:14:21 -0500 Original-Newsgroups: gnu.emacs.help Mail-Copies-To: nobody User-Agent: MT-NewsWatcher/3.5.2 (PPC Mac OS X) X-Copies-To: never Original-Lines: 20 Original-NNTP-Posting-Host: 24.34.108.171 Original-X-Trace: sv3-AE8Y4cwX8wDBh8Hg2gls8JBLjkGJQohO45g9x2rlJyiv8j1cflkri81w8ArrlDjPvOCCwVxSUWg9qs4!0QO5dwE1zEMfznCWUXrXNIbe1nAsaQF9p3zc4kYHpFJ3jGyFcRXKrEyzp1Bfms/lkMst4DXdaHzn!IpYL1+YyRdvQrSE1MOsd46Wx38ZB7MD+5pabBLGrgA== Original-X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.34 Original-Xref: shelby.stanford.edu gnu.emacs.help:149221 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:44806 Archived-At: In article <87myzbktwu.fsf@lion.rapttech.com.au>, Tim X wrote: > The timer will probably achieve what you want, but its not done asynchrously > in > the true sense. If the operation associated with the timer is resource > intensive or long running, you are very likely to observe 'freezes'. That's still truly asynchronous. Asynchronous means that something happens automatically when some condition occurs, rather than being part of the sequential operation of the program. Whether the main operation of the program continues in parallel is an orthogonal issue. -- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** *** PLEASE don't copy me on replies, I'll read them in the group ***