Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Jim Cheetham <jim@gonzul.net>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] any testimonials from users who transitioned from mutt?
Date: Thu, 20 Sep 2012 12:12:54 +1200	[thread overview]
Message-ID: <CA+2knquXHSnK=uBoNCFDG6q58o4+S4k5AHNi86dVnH6PQmDsuA@mail.gmail.com> (raw)
In-Reply-To: <20120919215657.GA17624@lifeintegrity.com>

On Thu, Sep 20, 2012 at 9:56 AM, Allan Wind
<allan_wind@lifeintegrity.com> wrote:
> On 2012-09-19 14:15:00, Naveen Nathan wrote:
> sup, afaik, is dead <http://masanjin.net/>:
>
> I leave behind me the wreckage of unmaintained or handed-off
> projects:
> ...
> Sup, an email client for people with lots of mail.
>
> You may, however, want to check out <http://notmuchmail.org/> and
> <https://github.com/karelzak/mutt-kz>

Well, I've moved on from sup because of the non-maintained status, and
problems with gpgme versions.
Now running heliotrope/turnsole, and in general it's fine, almost as
good as sup but with many more rough edges. Turnsole crashes a lot,
which isn't a big problem because state is in heliotrope & not the
client; but some features seem to be missing completely -- I haven't
figured out GPG signing yet. I expect that before_add hooks would need
in heliotrope and I haven't looked for them yet.

However, looking at the original post, perhaps notmuch with mutt
integration (i.e. it creates temporary folders based on searches)
would suit well?

-jim
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2012-09-20  0:13 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 [this message]
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='CA+2knquXHSnK=uBoNCFDG6q58o4+S4k5AHNi86dVnH6PQmDsuA@mail.gmail.com' \
    --to=jim@gonzul.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