From: Naveen Nathan <naveen@lastninja.net>
To: sup-talk@rubyforge.org
Subject: [sup-talk] any testimonials from users who transitioned from mutt?
Date: Wed, 19 Sep 2012 14:15:00 -0700 [thread overview]
Message-ID: <20120919211500.GH48050@armakuni.lastninja.net> (raw)
Hi,
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 was wondering if any mutt users who use some of the above features
mentioned would mind sharing their experience after transitioning to Sup.
Although I wouldn't be surprised if people still continue to use both.
- Naveen
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2012-09-19 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 21:15 Naveen Nathan [this message]
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
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=20120919211500.GH48050@armakuni.lastninja.net \
--to=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