all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Jean Louis <guix@rcdrun.com>
Cc: help-guix@gnu.org
Subject: Re: guix edit mutt -- with new option, and dependency, how I got it working
Date: Thu, 10 Mar 2016 15:45:51 -0500	[thread overview]
Message-ID: <20160310204551.GA7510@jasmine> (raw)
In-Reply-To: <20160310065806.GA2618@protected.rcdrun.com>

On Thu, Mar 10, 2016 at 07:58:06AM +0100, Jean Louis wrote:
> Hello Leo,
> 
> I was using mutt on Debian, that option was always included:
> header_cache
> 
> - mutt accesses remote emails
> - this speeds up everything
> - GuixSD already includes gdbm and tokyocabinet
> - I have chosen gdbm, but testing could show if else is better
> 
> Imagine, when you have 2000-3000 emails, one need to wait long time, for
> mutt to read all the headers, seconds. This way it is 1 second. 
> 
> It should be included by default, as GuixSD does have external database
> libraries.

I'm really glad you mentioned this on our list! My "Archive" mail folder
has ~30000 messages, and I rarely opened it because of how long it would
take Mutt to load them all. With this option enabled, it loads almost
instantly, once the cache is created.

:)

I agree that we should build our Mutt with this option enabled.

If everyone agrees, the question is which database to use — we have gdbm
and bdb in our package tree (I think tokyocabinet is a WIP). I have no
idea which database is a better choice. What do people think?

  reply	other threads:[~2016-03-10 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  0:44 guix edit mutt -- with new option, and dependency, how I got it working Jean Louis
2016-03-10  1:45 ` Leo Famulari
2016-03-10  6:58   ` Jean Louis
2016-03-10 20:45     ` Leo Famulari [this message]
2016-03-10 21:06       ` Efraim Flashner
2016-03-10 21:34         ` Leo Famulari
2016-03-11 13:37           ` Ludovic Courtès

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=20160310204551.GA7510@jasmine \
    --to=leo@famulari.name \
    --cc=guix@rcdrun.com \
    --cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.