From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: What's the problem? Date: 10 Dec 2003 14:51:08 +0900 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <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> <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 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1071035663 30688 80.91.224.253 (10 Dec 2003 05:54:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 10 Dec 2003 05:54:23 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Dec 10 06:54:20 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 1ATxIi-0006nt-00 for ; Wed, 10 Dec 2003 06:54:20 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ATxIh-0000yT-00 for ; Wed, 10 Dec 2003 06:54:20 +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 1ATyDo-0004jB-OS for emacs-devel@quimby.gnus.org; Wed, 10 Dec 2003 01:53:20 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ATyDj-0004iu-P5 for emacs-devel@gnu.org; Wed, 10 Dec 2003 01:53:15 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ATyDD-0004dx-4d for emacs-devel@gnu.org; Wed, 10 Dec 2003 01:53:14 -0500 Original-Received: from [210.143.35.52] (helo=TYO202.gate.nec.co.jp) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ATyDC-0004dm-GC; Wed, 10 Dec 2003 01:52:42 -0500 Original-Received: from mailgate4.nec.co.jp (mailgate53.nec.co.jp [10.7.69.184]) by TYO202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id hBA5pBM07560; Wed, 10 Dec 2003 14:51:11 +0900 (JST) Original-Received: (from root@localhost) by mailgate4.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id hBA5pBs29417; Wed, 10 Dec 2003 14:51:11 +0900 (JST) Original-Received: from edtmg02.lsi.nec.co.jp ([10.26.16.202]) by mailsv.nec.co.jp (8.11.7/3.7W-MAILSV-NEC) with ESMTP id hBA5pAF03190; Wed, 10 Dec 2003 14:51:10 +0900 (JST) Original-Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edtmg02.lsi.nec.co.jp (8.9.3p2+3.2W/3.7W_EDC_Ver.1.0) with ESMTP id OAA07986; Wed, 10 Dec 2003 14:51:09 +0900 (JST) Original-Received: from localhost (mcspd15 [10.30.114.174]) by mcsss2.ucom.lsi.nec.co.jp (8.12.10/8.12.8/EDcg v2.01-mc/1046780839) with ESMTP id hBA5p87Q028917; Wed, 10 Dec 2003 14:51:08 +0900 (JST) Original-Received: by localhost (Postfix, from userid 31295) id D9E4310096; Wed, 10 Dec 2003 14:51:08 +0900 (JST) Original-To: Juri Linkov System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: Original-Lines: 30 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:18606 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18606 Simon Josefsson writes: > > It depends on your environment of course -- if you have a slow network > > connection (or a slow server), it can spend a _lot_ of time waiting for > > external processes/data. > > Right, with emphasis on _can_. At least for me, this is an issue every single day; the CPU-bound parts of summary generation &c are slightly annoying, but really not enough to warrant any massive rewriting -- on the order of 30s or so for a large newsgroup -- but IO-bound delays can be 10 _minutes_. I don't know what it's like for other people. > > Anyway my main point is that I think it's basically an application > > issue, though emacs might help by adding helper functions. > > I don't see how fixing my perceived problem can be done without some > kind of threading support in Emacs (co-operative or whatever). Hence, > helper functions would do more than just help, they are critical in > improving the application. 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. -Miles -- Run away! Run away!