From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Maildir++ subfolders
Date: Tue, 15 Sep 2020 08:59:40 -0700 [thread overview]
Message-ID: <87o8m7xc7n.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ft7j1e9y.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Tuesday, 15 Sep 2020 at 14:04, Kevin Shell wrote:
>> I'm big fan of Maildir/Maildir++ format.
>
> I also am a big fan of this format, especially as I read email on
> different systems with synchronized file systems. Maildir is ideal to
> avoid inconsistent systems or overwriting.
>
> However, nnmaildir does not scale well, having what I estimate to be
> O(n^3) time to rescan/re-index folders. With large nnmaildir folders
> (>10000 messages), nnmaildir becomes unusable.
When I do get to nnmaildir, the two main things I want to do are to
allow for dot-prefixed folder layouts, and to find a way to allow more
control of the indexing of messages. At the very least we could start by
letting users shut off nov generation entirely. That would slow down
header generation, but other access would be instant. Ideally we'd be
able to have a "index on first access" option, which might be the best
of both worlds.
next prev parent reply other threads:[~2020-09-15 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 5:46 Kevin Shell
2020-09-14 5:55 ` Kevin Shell
2020-09-14 21:27 ` Eric Abrahamsen
2020-09-15 0:10 ` Kevin Shell
2020-09-15 4:13 ` Eric Abrahamsen
2020-09-15 6:04 ` Kevin Shell
2020-09-15 11:16 ` Eric S Fraga
2020-09-15 15:59 ` Eric Abrahamsen [this message]
2020-09-16 14:45 ` Eric S Fraga
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=87o8m7xc7n.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
/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).