From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.devel Subject: Re: What's the problem? Date: Wed, 10 Dec 2003 10:18:17 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <1190-Wed10Dec2003101817+0200-eliz@elta.co.il> References: <4nllpt3hr3.fsf@lockgroove.bwh.harvard.edu> <5bad69zd43.fsf@lister.roxen.com> <4noeuon378.fsf@lockgroove.bwh.harvard.edu> <4ny8tsgxy6.fsf@lockgroove.bwh.harvard.edu> <4nhe0ggv0u.fsf@lockgroove.bwh.harvard.edu> <4nk75bwjaf.fsf@lockgroove.bwh.harvard.edu> <4nsmjv8d32.fsf@collins.bwh.harvard.edu> <87iskpbloe.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1071044494 10561 80.91.224.253 (10 Dec 2003 08:21:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 10 Dec 2003 08:21:34 +0000 (UTC) Cc: juri@jurta.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Dec 10 09:21:28 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 1ATzb6-0003Hi-00 for ; Wed, 10 Dec 2003 09:21:28 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ATzb6-0003Km-00 for ; Wed, 10 Dec 2003 09:21:28 +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 1AU0XI-0000I1-Ub for emacs-devel@quimby.gnus.org; Wed, 10 Dec 2003 04:21:36 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AU0XD-0000Fx-GU for emacs-devel@gnu.org; Wed, 10 Dec 2003 04:21:31 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AU0Wh-000864-GJ for emacs-devel@gnu.org; Wed, 10 Dec 2003 04:21:30 -0500 Original-Received: from [192.114.186.22] (helo=gollum.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AU0Wg-00083C-RP for emacs-devel@gnu.org; Wed, 10 Dec 2003 04:20:59 -0500 Original-Received: from zaretski ([80.230.154.120]) by gollum.inter.net.il (Mirapoint Messaging Server MOS 3.3.8-GR) with ESMTP id CAB94613; Wed, 10 Dec 2003 10:19:30 +0200 (IST) Original-To: emacs-devel@gnu.org X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: (message from Simon Josefsson on Wed, 10 Dec 2003 07:34:45 +0100) 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:18613 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18613 > From: Simon Josefsson > Date: Wed, 10 Dec 2003 07:34:45 +0100 > > > > What I'm trying to say is that the `threading support' need not be > > particularly good, or general-purpose. Probably something could be > > hacked up right _now_, without any additional core functions, using > > clever programming and emacs timers, by changing the worst-offending > > part of the gnus code into something event driven. > > I don't understand. How would making the summary buffer generation > asynchronous stop Emacs from locking up during computations? For me, > the summary buffer generation is CPU bound in elisp, not IO bound. By doing the computation in chunks, like stealth font-lock does, for example, you let other tasks get slots of CPU time while the long computation runs. It's like telling the user to go for a coffee while Gnus computes the summary buffer, only instead of coffee she can type away something in another buffer ;-)