From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Slow opening of threads?
Date: Fri, 22 Oct 2010 19:02:39 +0100 [thread overview]
Message-ID: <1287770413-sup-279@blake> (raw)
In-Reply-To: <1287752579-sup-8292@niflheimr>
[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]
> I heard rumours that notmuch is supposed to be significantly faster than sup
> with huge amounts of mail, while also being tag-based. If you don't mind using
> emacs, which is - I think - the only usable interface to it, you could give it
> a try (sorry for promoting different mailclients here :)
Oh gods. I'm emacs-phobic.
But I can live with Sup taking an age to open threads every so often, at least until I reorganise away from NFS and/or it gets fixed.
I love Sup for Ruby-ness as much as anything. The other day I had a corrupt index and I fixed it myself! </smug>
--
Advice from an old carpenter: measure twice, saw once.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-10-22 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 9:23 Shadowfirebird
2010-10-22 10:40 ` Amadeusz Żołnowski
2010-10-22 11:48 ` Shadowfirebird
2010-10-22 13:09 ` Moritz Wilhelmy
2010-10-22 18:02 ` Shadowfirebird [this message]
2010-10-22 23:32 ` Moritz Wilhelmy
2010-10-22 11:04 ` Gaute Hope
2010-10-22 11:16 ` Philipp Überbacher
2010-10-22 12:21 ` Ben Walton
2010-10-22 12:38 ` Mark Alexander
2010-10-22 13:03 ` Shadowfirebird
2010-10-22 16:28 ` Mark Alexander
2010-10-22 17:19 ` Sascha Silbe
2010-10-22 19:56 ` Shadowfirebird
2010-10-23 8:28 ` Sascha Silbe
2010-10-23 10:42 ` Shadowfirebird
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=1287770413-sup-279@blake \
--to=shadowfirebird@gmail.com \
--cc=sup-talk@rubyforge.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