From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61487 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: nnimap check for new mail in the background Date: Sat, 10 Dec 2005 12:39:02 +0100 Message-ID: References: <87irtzhs6x.fsf@ntnu.no> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1134215190 28969 80.91.229.2 (10 Dec 2005 11:46:30 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 10 Dec 2005 11:46:30 +0000 (UTC) Original-X-From: ding-owner+m10019@lists.math.uh.edu Sat Dec 10 12:46:23 2005 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1El3A1-0006uA-EK for ding-account@gmane.org; Sat, 10 Dec 2005 12:45:06 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1El39s-0003jq-00; Sat, 10 Dec 2005 05:44:56 -0600 Original-Received: from nas01.math.uh.edu ([129.7.128.39]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1El34S-0003ji-00 for ding@lists.math.uh.edu; Sat, 10 Dec 2005 05:39:20 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas01.math.uh.edu with esmtp (Exim 4.52) id 1El34Q-0001sH-Kc for ding@lists.math.uh.edu; Sat, 10 Dec 2005 05:39:20 -0600 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1El34L-0006gZ-00 for ; Sat, 10 Dec 2005 12:39:13 +0100 Original-Received: from latte.josefsson.org (jas@yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3) with ESMTP id jBABd6fL006671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 10 Dec 2005 12:39:07 +0100 Original-To: ding@gnus.org OpenPGP: id=B565716F; url=http://josefsson.org/key.txt X-Hashcash: 1:21:051210:ding@gnus.org::sXpK1hVXBWXZTy2g:D38b In-Reply-To: <87irtzhs6x.fsf@ntnu.no> (Lars Tobias =?iso-8859-1?Q?B=F8rsti?= =?iso-8859-1?Q?ng's?= message of "Fri, 09 Dec 2005 04:20:38 +0100") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on yxa-iv X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on yxa.extundo.com X-Virus-Status: Clean X-MIME-Autoconverted: from 8bit to quoted-printable by yxa.extundo.com id jBABd6fL006671 X-Spam-Score: -2.6 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:61487 Archived-At: Lars Tobias B=F8rsting writes: > Hi, > > I have used Gnus for a couple of years now, and can't live without > it. I have just switched from getting mail via mbox spool to nnimap, > with CourierIMAP on the server. I have moved my dozens of mail groups > to nnimap groups. I like IMAP very much, except for one thing; it's very > slow to check for new mail. > > With the nnmail backend, checking some dozens of groups was instant and > unnoticable. With nnimap, it's painfully slow. That would have been OK > if I could use Gnus in the meantime. However it locks up, showing > "nnimap: updating info for folder xxx...done" until it is done. This is > making me wait for about one minute until I can do something again. It should not print the "Updating info" messages -- that will be much slower than regular new mail checking. It should only say "Quickly checking mailbox foo", for each nnimap mailbox. Historically, the reason for the "update info" message was that your groups' server method (type `G e' on the group in the *Group* buffer) said (nnimap "foo") rather than "nnimap:foo". Changing the former into to the latter would solve the problem. However, recently (perhaps last month) I have noticed that Gnus CVS say "Updating info" for me too. Not always, but sometimes. So I think we have another bug. > Is it possible to do new mail checking in a separate thread that runs in > the background, so that it doesn't lock up the interface? If not, is it > hard to implement such a feature? It should be possible. Implement something run with the idle timer and iterate over all groups. The problem is in informing Gnus about the update -- there is no clean API to do that. It could be added, but I don't know how. You could also try to fix the bug above, the "Quickly checking" test is fairly quick.