From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Benjamin Riefenstahl Newsgroups: gmane.emacs.devel Subject: Re: Are there plans for a multi-threaded Emacs? Date: Fri, 05 Dec 2003 14:56:14 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <87oevbes4h.fsf@emacswiki.org> <20031117040607.C6C5D79B72@server2.messagingengine.com> <87ekvpx18d.fsf@emptyhost.emptydomain.de> <4nad6cikxy.fsf@holmes.bwh.harvard.edu> <4nllpt3hr3.fsf@lockgroove.bwh.harvard.edu> <5bad69zd43.fsf@lister.roxen.com> <4noeuon378.fsf@lockgroove.bwh.harvard.edu> <5bptf4ebw8.fsf@lister.roxen.com> <4nu14ggwvq.fsf@lockgroove.bwh.harvard.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1070632868 11127 80.91.224.253 (5 Dec 2003 14:01:08 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 5 Dec 2003 14:01:08 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Dec 05 15:01:05 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ASGW1-0003zw-00 for ; Fri, 05 Dec 2003 15:01:05 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ASGW0-00040N-00 for ; Fri, 05 Dec 2003 15:01:04 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ASHRq-0006NO-8X for emacs-devel@quimby.gnus.org; Fri, 05 Dec 2003 10:00:50 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ASHQd-00066K-39 for emacs-devel@gnu.org; Fri, 05 Dec 2003 09:59:35 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ASHQ3-0005vc-JW for emacs-devel@gnu.org; Fri, 05 Dec 2003 09:59:30 -0500 Original-Received: from [193.28.100.166] (helo=mail.epost.de) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ASHQ3-0005v5-2j for emacs-devel@gnu.org; Fri, 05 Dec 2003 09:58:59 -0500 Original-Received: from seneca.benny.turtle-trading.net.epost.de (193.99.153.30) by mail.epost.de (6.7.019) id 3FA8306E003F6DD0; Fri, 5 Dec 2003 14:57:31 +0100 Original-To: Ted Zlatanov In-Reply-To: <4nu14ggwvq.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 04 Dec 2003 15:18:17 -0500") User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18416 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18416 Hi Ted, Just an immediate reaction to your examples: Ted Zlatanov writes: > font-locking a buffer; Isn't font-locking done in parallel (in a cooperative manner) already with lazy-lock? > reading or writing a file. Reading, yes, but writing, I'm not so sure. I think usually I want to be sure that a file is completely written, before I start some other action. Also I'm sure that both reading and writing can be done asynchronously without having all of Emacs being multi-threaded. Even if you don't have support from the OS this can be implemented with cooperative means, just reading/writing reasonable chunks during idle time. benny