From: prj@po.cwru.edu (Paul Jarc)
Subject: patch: nnmaildir commentary, etc.
Date: Fri, 21 Dec 2001 17:43:58 -0500 [thread overview]
Message-ID: <m3k7vgi46z.fsf@multivac.cwru.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
Just some cleanups to make nnmaildir more at home in CVS.
* gnus.el (gnus-valid-select-methods): Include nnmaildir.
* nnmaildir.el (top-level): Add commentary.
(nnmaildir-version): Indicate that nnmaildir is now a standard
part of Gnus, not separately released.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: nnmaildir.diff --]
[-- Type: text/x-patch, Size: 2572 bytes --]
Index: lisp/gnus.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus.el,v
retrieving revision 6.67
diff -u -r6.67 gnus.el
--- lisp/gnus.el 2001/12/19 14:35:02 6.67
+++ lisp/gnus.el 2001/12/21 22:46:24
@@ -1395,7 +1395,8 @@
("nnwarchive" none)
("nnlistserv" none)
("nnagent" post-mail)
- ("nnimap" post-mail address prompt-address physical-address))
+ ("nnimap" post-mail address prompt-address physical-address)
+ ("nnmaildir" mail respool address))
"*An alist of valid select methods.
The first element of each list lists should be a string with the name
of the select method. The other elements may be the category of
Index: lisp/nnmaildir.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/nnmaildir.el,v
retrieving revision 6.2
diff -u -r6.2 nnmaildir.el
--- lisp/nnmaildir.el 2001/12/20 20:40:32 6.2
+++ lisp/nnmaildir.el 2001/12/21 22:46:24
@@ -23,7 +23,30 @@
;;; Commentary:
-;;; <URL:http://multivac.cwru.edu./nnmaildir/>
+;; Maildir format is documented in the maildir(5) man page from qmail
+;; and at <URL:http://cr.yp.to/proto/maildir.html>. nnmaildir also
+;; stores extra information in the .nnmaildir/ directory within a
+;; maildir.
+;;
+;; Some goals of nnmaildir:
+;; * Everything Just Works, and correctly. E.g., stale NOV data is
+;; ignored when articles have been edited; no need for
+;; -generate-nov-databases.
+;; * Perfect reliability: [C-g] will never corrupt its data in memory,
+;; and SIGKILL will never corrupt its data in the filesystem.
+;; * We make it easy to manipulate marks, etc., from outside Gnus.
+;; * All information about a group is stored in the maildir, for easy
+;; backup and restoring.
+;; * Use the filesystem as a database.
+;;
+;; Todo:
+;; * Ignore old NOV data when gnus-extra-headers has changed.
+;; * Don't force article renumbering, so nnmaildir can be used with
+;; the cache and agent. Alternatively, completely rewrite the Gnus
+;; backend interface, which would have other advantages.
+;;
+;; See also <URL:http://multivac.cwru.edu./nnmaildir/> until that
+;; information is added to the Gnus manual.
;;; Code:
@@ -39,8 +62,7 @@
(require 'cl)
(require 'nnmail))
-(gnus-declare-backend "nnmaildir" 'mail 'respool 'address)
-(defconst nnmaildir-version "2001.12.19")
+(defconst nnmaildir-version "Gnus")
(defvar nnmaildir-article-file-name nil
"*The filename of the most recently requested article. This variable is set
[-- Attachment #3: Type: text/plain, Size: 7 bytes --]
paul
next reply other threads:[~2001-12-21 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 22:43 Paul Jarc [this message]
2001-12-21 23:00 ` ShengHuo ZHU
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3k7vgi46z.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).