From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.117.70 with SMTP id kc6cs145085vdb; Fri, 27 Jan 2012 21:45:50 -0800 (PST) Received: by 10.224.86.201 with SMTP id t9mr11945587qal.95.1327729549611; Fri, 27 Jan 2012 21:45:49 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org. [205.234.109.19]) by mx.google.com with ESMTP id dl6si8555669qab.19.2012.01.27.21.45.49; Fri, 27 Jan 2012 21:45:49 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C85711678369; Sat, 28 Jan 2012 00:45:48 -0500 (EST) X-Greylist: delayed 1709 seconds by postgrey-1.31 at rubyforge.org; Sat, 28 Jan 2012 00:42:10 EST Received: from mail.copilotco.com (mail.copilotco.com [216.105.40.123]) by rubyforge.org (Postfix) with ESMTP id 32E851858300 for ; Sat, 28 Jan 2012 00:42:09 -0500 (EST) Received: from tracyreed.org (unknown [10.9.8.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.copilotco.com (Postfix) with ESMTP id 56BA064C3E; Fri, 27 Jan 2012 21:13:34 -0800 (PST) Date: Fri, 27 Jan 2012 21:14:14 -0800 From: Tracy Reed To: Allan Wind Message-ID: <20120128051414.GB3481@tracyreed.org> References: <1327301754-sup-3169@lifeintegrity.com> MIME-Version: 1.0 In-Reply-To: <1327301754-sup-3169@lifeintegrity.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: sup-talk Subject: Re: [sup-talk] First impressions X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0295577237==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============0295577237== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="St7VIuEGZ6dlpu13" Content-Disposition: inline --St7VIuEGZ6dlpu13 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 mut= t but > first impressions are shaky. =20 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. Wh= ile I love the tagging and configurability via a nice programming language I fo= und it crashed a lot too. --=20 Tracy Reed http://tracyreed.org Digital signature attached for your safety. --St7VIuEGZ6dlpu13 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFPI4QmBhSTPg0d/nQRAh1FAJ462ps8I0R+L7sSWEmIUd91OGcmAACfX8ii jIAp+R3lnIixYgqDlMVK/wo= =xWQV -----END PGP SIGNATURE----- --St7VIuEGZ6dlpu13-- --===============0295577237== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============0295577237==--