From: Tracy Reed <treed@ultraviolet.org>
To: Allan Wind <allan_wind@lifeintegrity.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] First impressions
Date: Fri, 27 Jan 2012 21:14:14 -0800 [thread overview]
Message-ID: <20120128051414.GB3481@tracyreed.org> (raw)
In-Reply-To: <1327301754-sup-3169@lifeintegrity.com>
[-- Attachment #1.1: Type: text/plain, Size: 692 bytes --]
On Mon, Jan 23, 2012 at 01:58:14AM -0500, Allan Wind spake thusly:
> I was trying to see if sup v0.12.1 would be a suitable alternative to mutt but
> first impressions are shaky.
I went through the very same process. I've given up on sup and am sticking with
mutt for the time being.. The developers aren't really doing anything with sup
other than minor bug fixes. They prefer to work on heliotrope which is the
successor to sup. sup itself doesn't have a future as far as I can tell. While
I love the tagging and configurability via a nice programming language I found
it crashed a lot too.
--
Tracy Reed
http://tracyreed.org
Digital signature attached for your safety.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2012-01-28 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 6:58 Allan Wind
2012-01-28 5:14 ` Tracy Reed [this message]
2012-01-28 18:38 ` Allan Wind
2012-01-28 19:32 ` Patrick Totzke
2012-01-28 21:06 ` Allan Wind
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=20120128051414.GB3481@tracyreed.org \
--to=treed@ultraviolet.org \
--cc=allan_wind@lifeintegrity.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