From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/6534 Path: main.gmane.org!not-for-mail From: Sudish Joseph Newsgroups: gmane.emacs.gnus.general Subject: Re: Gnus v5.2.8 is released Date: 05 Jun 1996 21:48:21 -0400 Sender: sj@atreides.erehwon.org Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035146974 3918 80.91.224.250 (20 Oct 2002 20:49:34 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:49:34 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id TAA19301 for ; Wed, 5 Jun 1996 19:06:57 -0700 Original-Received: from atreides.erehwon.org (sj@atl-ga16-02.ix.netcom.com [204.32.174.130]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Thu, 6 Jun 1996 03:45:13 +0200 Original-Received: (from sj@localhost) by atreides.erehwon.org (8.7.5/8.6.9) id VAA00178; Wed, 5 Jun 1996 21:48:21 -0400 Original-To: ding@ifi.uio.no In-Reply-To: Lars Magne Ingebrigtsen's message of 05 Jun 1996 17:34:01 +0000 Original-Lines: 57 X-Mailer: Gnus v5.2.7/Emacs 19.31 Xref: main.gmane.org gmane.emacs.gnus.general:6534 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:6534 Lars Magne Ingebrigtsen writes: > Tue Jun 4 13:46:45 1996 Scott Byer [ Lots of cool speedups for nnfolder. ] On the subject of mail speedups, it'd be nice if nnmail-get-new-mail didn't loop over all the specified spools for every single group. This doesn't seem like a speed hit when all you're paying is a stat on an guaranteed-to-be-empty spool file for all groups after the first...but it's -huge- when one of those spools is a pop server accessed over a PPP link. I'd even consider this a bug. :-) I thought it'd be a simple tweak to nnmail-get-spool-files, and I still do. But I'm not too clear on the interaction with summary-local settings of nnmail-spool-file (i.e., from the group params). I also spent all my time wandering around with my jaw open inside the aladdin's cave of nnoo.el (very very kewl, Lars). Should have known better than to breeze into Lars's code after 5-6 months expecting things to stay the same. If someone would clarify/enumerate the ways in which spool files can be specified and/or modified on a per-group basis, I'll fix this over the weekend (gonna read CoS till then :-). [ Unrelated, but I'll throw it in here ] Maybe we should stare long and hard at the different sources of messages, and how they differ. Right now, it's still somewhat random as to how different backends access new messages--I mean how the user specifies the source of new messages, nnoo unifies the actual code nicely. For instance, most mail backends will get mail from the central spool. The central spool is split into every group and should be accessed just once per get-new-news cycle. Some groups will have their own spools (nnmail-use-procmail). POP is akin to a central spool. News, OTOH, always has a unique source per group. IMAP will use *both* methods. It'd be nice if there was a way of specifying the characteristics of a backend, so that nnmail-get-new-mail could be intelligent about how often and when to access the spools for a given backend, w/o having that information hardcoded. It'd also make it easier to make GNUS extensible in the sense of being able to 1) add nnfoo.elc to your load-path 2) set a few variables that completely specify it's behaviour 3) call a GNUS-provided function to register itself with GNUS. and have it work just as well as any native backend. nnoo goes a long way towards this already. -- Sudish