From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Concurrency Date: Mon, 29 Mar 2010 13:39:36 -0400 Message-ID: References: <27349166.post@talk.nabble.com> <27563610.post@talk.nabble.com> <4B7564C7.1010309@swipnet.se> <27564728.post@talk.nabble.com> <4B756FB7.3050202@swipnet.se> <87k4ui4gik.fsf@lola.goethe.zz> <27566385.post@talk.nabble.com> <87wryi2sjd.fsf@lola.goethe.zz> <27585994.post@talk.nabble.com> <87k4ucdmwh.fsf@stupidchicken.com> <87d3zweq4e.fsf@master.homenet> <87y6hg1h4a.fsf@thor.thematica.it> <87tys3j9fa.fsf@lifelogs.com> <87eij6tqmu.fsf@lifelogs.com> <0313BE4F-1CA1-4CFD-9CF9-ADA3AFF9ECF3@raeburn.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1269884610 18094 80.91.229.12 (29 Mar 2010 17:43:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 29 Mar 2010 17:43:30 +0000 (UTC) Cc: Ken Raeburn , "emacs-devel@gnu.org discussions" To: Tom Tromey Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 29 19:43:26 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NwIyr-00042f-Vq for ged-emacs-devel@m.gmane.org; Mon, 29 Mar 2010 19:43:25 +0200 Original-Received: from localhost ([127.0.0.1]:49074 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NwIyk-0006D6-EL for ged-emacs-devel@m.gmane.org; Mon, 29 Mar 2010 13:42:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NwIw9-000519-8X for emacs-devel@gnu.org; Mon, 29 Mar 2010 13:39:41 -0400 Original-Received: from [140.186.70.92] (port=53261 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NwIw7-0004zk-Fd for emacs-devel@gnu.org; Mon, 29 Mar 2010 13:39:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NwIw5-0004xg-VR for emacs-devel@gnu.org; Mon, 29 Mar 2010 13:39:39 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:55597 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NwIw5-0004xT-RH for emacs-devel@gnu.org; Mon, 29 Mar 2010 13:39:37 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAAuDsEtLd/h9/2dsb2JhbACbJHLAKYUBBIse X-IronPort-AV: E=Sophos;i="4.51,329,1267419600"; d="scan'208";a="59746065" Original-Received: from 75-119-248-125.dsl.teksavvy.com (HELO pastel.home) ([75.119.248.125]) by ironport2-out.pppoe.ca with ESMTP; 29 Mar 2010 13:39:36 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 13ECC85F0; Mon, 29 Mar 2010 13:39:36 -0400 (EDT) In-Reply-To: (Tom Tromey's message of "Mon, 29 Mar 2010 10:49:07 -0600") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:122858 Archived-At: Tom> * Suppose you have existing elisp that creates a process with a filter, Tom> and the filter changes a let-bound variable, and the "outer" elisp Tom> blocks in sit-for waiting for the filter to do its thing. Nothing in Tom> the current code guarantees that the process filter will be run in the Tom> "correct" thread. Ken> That may be a reason to force the filter to run in the same thread Ken> that created it. > Yeah. I was thinking perhaps process filters could have a thread > attribute, which would default to their creating thread. Setting this > to nil could mean that the process filter could run in any thread. Or maybe accept-process-output should cause the filters to be run in the waiting thread (especially when the `proc' argument is provided). Stefan