From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/32899 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.emacs.gnus.general Subject: Re: "Fixing up" gnus - (how hard is this?). (was Re: (provide 'nnmaildir)) Date: 19 Oct 2000 12:05:00 -0400 Sender: owner-ding@hpc.uh.edu Message-ID: References: <87aec3o3u6.fsf_-_@raven.localnet> <871yxfnlnz.fsf@raven.localnet> <87g0lt9amk.fsf@raven.localnet> <87hf697kba.fsf@raven.localnet> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035169105 22364 80.91.224.250 (21 Oct 2002 02:58:25 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:58:25 +0000 (UTC) Return-Path: Original-Received: from spinoza.math.uh.edu (spinoza.math.uh.edu [129.7.128.18]) by mailhost.sclp.com (Postfix) with ESMTP id 6B879D051E for ; Thu, 19 Oct 2000 12:06:43 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by spinoza.math.uh.edu (8.9.1/8.9.1) with ESMTP id LAB02605; Thu, 19 Oct 2000 11:06:21 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 19 Oct 2000 11:05:17 -0500 (CDT) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id LAA13996 for ; Thu, 19 Oct 2000 11:05:06 -0500 (CDT) Original-Received: from multivac.student.cwru.edu (multivac.STUDENT.CWRU.Edu [129.22.239.69]) by mailhost.sclp.com (Postfix) with SMTP id 8D56FD051E for ; Thu, 19 Oct 2000 12:05:23 -0400 (EDT) Original-Received: (qmail 29925 invoked by uid 500); 19 Oct 2000 16:05:22 -0000 Mail-Followup-To: ding@gnus.org Original-To: ding@gnus.org In-Reply-To: Rob Browning's message of "18 Oct 2000 19:20:57 -0500" Original-Lines: 53 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:32899 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:32899 Rob Browning writes: > So stepping back for a moment --- you've been working on an nnmaildir > backend, right? Right. . (This is a new URL; the old one will still work for a while too. I'll also get some documentation up there eventually.) > As it stands now, what are the advantages/differences of that from > nnmail? Well, mail is kept in the maildir it was delivered to, to begin with, so you don't have to worry about mbox From_ quoting, etc. nnmail backends can pull in mail from a maildir, but then store it differently (but not all of them quote From_, of course). See . I haven't measured, but I'd expect nnmaildir to compare well speedwise. Each message is in a separate file, and it generates a NOV line when a new message is first seen, so it should be comparable to nnml. While the server is open, a structure is kept in memory, that holds the NOV lines associated with each article; they're read from disk only at startup. Files are never rewritten, unless you edit an article, so the file's last-modified time gives you the delivery time. (Modulo an unsolved bug in -request-{move,accept}-article.) The file that stores group information, including NOV lines, is written frequently and reliably - the file ".nnmaildir" always exists (after it's been written once) and it's always consistent. I'm not very familiar with the nnmail backends, so I'm guessing where the differences are, somewhat. No splitting. (This is probably the big reason that nnmaildir doesn't inherit from nnmail.) Each maildir is a group. Assuming you use qmail with maildir delivery, it's easy to direct message to the appropriate maildir in the delivery process via .qmail files. Mailing list subscriptions are especially easy: as user prj, I control all prj-anything addresses along with prj itself, so I subscribe prj-ding to this list, and that address gets its own delivery instructions, directing messages into my ding maildir. The next version will store marks, in such a way that you should be able to use other maildir readers on the same maildir between Gnus sessions, and the two will see (some of) each others' marks. (Assuming the other reader uses the "2," info format described in the link above - I don't know if there are any such readers.) > I'm wondering if we might be able to work together to document the > backend interface better, I'd especially like to see documentation of what triggers each backend function, and what assumptions, if any, they can make about their environment - current buffer, etc. paul