From: Allan Wind <allan_wind@lifeintegrity.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] First impressions
Date: Sat, 28 Jan 2012 13:38:01 -0500 [thread overview]
Message-ID: <20120128183801.GF25519@lifeintegrity.com> (raw)
In-Reply-To: <20120128051414.GB3481@tracyreed.org>
On 2012-01-27 21:14:14, Tracy Reed wrote:
> 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.
Thanks Tracy.
/Allan
--
Allan Wind
Life Integrity, LLC
<http://lifeintegrity.com>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2012-01-28 18:46 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
2012-01-28 18:38 ` Allan Wind [this message]
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=20120128183801.GF25519@lifeintegrity.com \
--to=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