From: Steven Hum <sdothum@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] any testimonials from users who transitioned from mutt?
Date: Thu, 20 Sep 2012 18:25:23 -0400 [thread overview]
Message-ID: <1348177473-sup-7941@monad> (raw)
In-Reply-To: <1348123080-sup-7217@pruts.nl>
I have used mutt with notmuch for ages and thought I would never switch
until I came across sup recently. (notmuch, by the way is a very
competent search mechanism - I believe there is even a mutt fork afoot
to integrate it more seamlessly into mutt).
sup does not back sync to maildir which for me should be a deal breaker
as I like using offlineimap/imapfilter to maintain persistent mail on my
desktop and laptop which allows me to peruse and respond to emails even
when I am not connected to the Internet.
Alas, I find sup so compelling a mail client that I am, for now, willing
to put up with that serious lack. There are sup forks I have been
looking into that appear to address this issue - but I am not sure if
anyone is going to spearhead taking sup over officially to merge the
work done in this area.
The heliotrope/turnsole project is still not ready for prime time
- beyond installation for me at least, the turnsole client crashes
a lot. Even then, I am not sure if heliotrope will address the maildir
back sync issue (there is an imaptrope fork which may address this). If
it doesn't, it may not provide me with any benefit towards my offline
mail usage.
Like earlier posts, sup's tagging, smart conversation view (with only
unread messages expanded - I am not sure if even Google's web gmail
interface offers that) and facility to auto archive
threads/folders/whatever rules you wish, just makes the email process
more compelling and effective (for me) by eliminating inbox noise.
The big back sync issue, however, does mean sup is non-destructive, so
is worth a look if you are one of those people who is forever looking
for the perfect email client (that sucks less :-) mutt will stay on my
system if sup's maildir deficiency becomes intolerable - for now,
I foresee using it to periodically prune and manage my maildirs.
Steven
--
"Truth or die."
Steven Hum
5 - 28 Gilmour St
Ottawa, ON K2P 0N3
email sdothum@gmail.com
tel 613.237.9058
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2012-09-20 22:26 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
2012-09-20 22:25 ` Steven Hum [this message]
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=1348177473-sup-7941@monad \
--to=sdothum@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