From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Enabling header caching in mutt
Date: Mon, 21 Mar 2016 12:20:07 +0200 [thread overview]
Message-ID: <20160321102007.GA15020@debian-netbook> (raw)
In-Reply-To: <cover.1458527936.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On Sun, Mar 20, 2016 at 10:47:04PM -0400, Leo Famulari wrote:
> This patch builds mutt with support for header caching so that large
> mailboxes can be opened quickly.
>
> Without the header cache, each message's headers are processed before
> the mailbox can be used. For large mailboxes (>10000 messages), this can
> take minutes.
>
> To use the header cache, users must enable it in their configuration.
>
> It's following up on this:
> http://lists.gnu.org/archive/html/help-guix/2016-03/msg00055.html
>
> I checked, and bdb and gdbm are already both in mutt's build-time
> dependency graph (openldap refers to bdb and python refers to gdbm).
>
> I've chosen gdbm for it's small size and because it's a GNU project. If
> anyone says they prefer another database, then let's talk!
>
I've just tried this out on my machine. At first I didn't see any
change, but then I added `set header_cache = ~/.cache/mutt/` to my
.muttrc and I was blown away by the difference.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-21 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 2:47 [PATCH 0/1] Enabling header caching in mutt Leo Famulari
2016-03-21 2:47 ` [PATCH 1/1] gnu: mutt: Enable header caching Leo Famulari
2016-03-21 16:44 ` Ludovic Courtès
2016-03-21 20:49 ` Leo Famulari
2016-03-21 10:20 ` Efraim Flashner [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160321102007.GA15020@debian-netbook \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).