From: Alfredo Palhares <masterkorp@masterkorp.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] any testimonials from users who transitioned from mutt?
Date: Wed, 19 Sep 2012 23:47:19 +0200 [thread overview]
Message-ID: <1348090678-sup-2446@masterkorp.net> (raw)
In-Reply-To: <20120919211500.GH48050@armakuni.lastninja.net>
Excerpts from Naveen Nathan's message of Wed Sep 19 23:15:00 +0200 2012:
> 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.
What i notice the most, is *speed*, mutt gets unbearable on big mailboxes.
Also the label is approach is much better, just because having more than one label
in an thread can be very usefull.
Also prefer the UI, tudier for tilling WMs and smarthphones (altough mutt can be
customized)
> 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.
One thing about sup, is that you have to go cold turkey, sup does not sync
back to the mailbox. I solved that problem by placing it under tmux on a
24/7 avaliable server, so i just ssh to tmux, from the computer, cellphone,
public machine whatever.
I eventually want to migrate to heliotrope once a decent client shows up.
But if you're on mutt and dont bother about using only one client for email,
Sup is awesome
--
Regards,
Alfredo Palhares
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2012-09-19 21:56 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 [this message]
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=1348090678-sup-2446@masterkorp.net \
--to=masterkorp@masterkorp.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