From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Maildir backend
Date: Wed, 06 Mar 2002 11:40:27 -0500 [thread overview]
Message-ID: <m3k7spabu6.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <20020306103130.A4152@fr.thalesgroup.com> =?iso-8859-1?q?(J=E9r=F4me?= Marant's message of "Wed, 6 Mar 2002 10:31:30 +0100")
Jérôme Marant <jerome.marant@fr.thalesgroup.com> wrote:
> I've tried nnmaildir but I think that it is not satisfactory
> since it takes a lot of resources (mostly heavy duplication of
> files)
What do you mean?
> it is pretty slow (the more files there are the slower
> it starts).
Yes, I've got some ideas to improve that.
> no NOV,
What's wrong with NOV?
> and renaming files with respect to their status (read,
> signed, and so on).
I don't think the standard maildir flags-in-filename scheme is
sufficient to accomodate all of Gnus's marks (and certainly not
user-defined marks). We could have a different flags-in-filename
scheme that would be more accomodating, but it would be unrecognizable
to other maildir readers. Would that still be worthwhile for you?
What would be the advantages over nnmaildir's current mark system?
paul
next prev parent reply other threads:[~2002-03-06 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 9:31 Jérôme Marant
2002-03-06 16:40 ` Paul Jarc [this message]
2002-03-07 8:56 ` Jérôme Marant
2002-03-07 18:00 ` Paul Jarc
2002-03-08 12:11 ` Jérôme Marant
2002-03-08 16:37 ` Paul Jarc
2002-03-12 9:41 ` Jérôme Marant
2002-03-12 14:30 ` Paul Jarc
2002-03-13 10:51 ` Jérôme Marant
2002-03-13 16:26 ` Paul Jarc
2002-03-13 17:33 ` Matt Armstrong
2002-03-13 18:03 ` Paul Jarc
2002-03-08 16:37 ` Paul Jarc
2002-03-08 12:11 ` Jérôme Marant
2002-03-07 18:00 ` Paul Jarc
2002-03-07 8:56 ` Jérôme Marant
2002-03-06 16:40 ` Paul Jarc
2002-03-06 9:31 Jérôme Marant
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=m3k7spabu6.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).