From: Ico <sup@zevv.nl>
To: Naveen Nathan <naveen@lastninja.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] any testimonials from users who transitioned from mutt?
Date: Thu, 20 Sep 2012 08:43:53 +0200 [thread overview]
Message-ID: <1348123080-sup-7217@pruts.nl> (raw)
In-Reply-To: <20120919211500.GH48050@armakuni.lastninja.net>
> Mutt and mail savvy user here. It's my daily use client, I use a lot of
> it's features such as threading, tagging, header caching (for imap).
>
> What it truly lacks, even though slightly supported by IMAP, is full-body
> search of email, indexing, etc.
I've been a long time mutt user before switching to sup a few years ago. Mutt
indeed lacks proper searching and indexing, but for this I found mairix [1],
which with some scripting [2], .muttrc [3] configuration and a cronjob [4] can
be integrated into mutt pretty seamless.
I eventually switched to sup not mainly for of the indexing/searching, but
because of the unique way sup keeps track of threads.
Now that sup is pretty much dead I find myself poking around in the
source more and more often, but maybe it is about time to switch back to
mutt for more stability :(
1. http://www.rpcurnow.force9.co.uk/mairix/
2. ~/bin/searchmail
#!/bin/sh
echo -n "Search for: "
read expr
echo $expr
if [ "$expr" = "" ]; then
clear
mairix --help
read
exit
fi
mairix $expr
3. .muttrc
macro index <esc>s !searchmail\nc=searched\n
macro pager <esc>s !searchmail\nc=searched\n
4. crontab
*/10 * * * * ~/bin/mairix
--
:wq
^X^Cy^K^X^C^C^C^C
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2012-09-20 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 21:15 Naveen Nathan
2012-09-19 21:47 ` Alfredo Palhares
2012-09-19 21:56 ` Allan Wind
2012-09-20 0:12 ` Jim Cheetham
2012-09-20 6:43 ` Ico [this message]
2012-09-20 22:25 ` Steven Hum
2012-09-20 23:58 ` Matthieu Rakotojaona
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=1348123080-sup-7217@pruts.nl \
--to=sup@zevv.nl \
--cc=naveen@lastninja.net \
--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