From: Harry Putnam <reader@newsguy.com>
Subject: Re: announce: nnmaildir 2001.12.19
Date: Thu, 20 Dec 2001 14:48:46 -0800 [thread overview]
Message-ID: <m1zo4dmtw7.fsf@reader.newsguy.com> (raw)
In-Reply-To: <m3y9jz3s5c.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Wed, 19 Dec 2001 14:51:05 -0500")
prj@po.cwru.edu (Paul Jarc) writes:
> <URL:http://multivac.cwru.edu./nnmaildir/>
> One new function, nnmaildir-article-number-to-file-name, and two
> bugfixes: -request-retrieve-headers was assuming the article range was
> sorted in ascending order, which is not the case for [/ o]; and
> -open-server was assumed to be called before anything else, which is
> not always the case when defining a server in the *Server* buffer
> (thanks to Harry Putnam for helping to find this one).
Paul, I noticed a warning on our pages about skipping versions and
what it might cause, but I see no handy way to tell which version is
currently in use. Nothing in the *.el file to indicate version.
I already know my version was the previous release but seems there
should be some way to tell.
Also maybe a condensed version of the info on our pages as a
`comments' section. Findable with M-x finder-commentary.
I'm going to take a stab at that, and will send you the result.
Also, I've considered moving our discussion about nnmaildir from
gnu.emacs.gnus to here. It has gotten somewhat detailed.
There should be a private message on you incoming spool some where
with a detailed report, see:
From: Harry Putnam <reader@newsguy.com>
In-Reply-To: <m3g069t8ka.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message
of "Tue, 18 Dec 2001 00:12:47 -0500")
Date: Tue, 18 Dec 2001 11:15:22 -0800
Message-ID: <x7vgf4tk51.fsf@reader.newsguy.com>
next prev parent reply other threads:[~2001-12-20 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 19:51 Paul Jarc
2001-12-20 22:48 ` Harry Putnam [this message]
2001-12-21 4:41 ` Paul Jarc
2001-12-21 11:37 ` Harry Putnam
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=m1zo4dmtw7.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
/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).