From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.58.247.3 with SMTP id ya3csp437895vec; Thu, 20 Sep 2012 15:26:42 -0700 (PDT) Received: by 10.50.191.165 with SMTP id gz5mr3033348igc.50.1348180001031; Thu, 20 Sep 2012 15:26:41 -0700 (PDT) Return-Path: Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com. [50.56.192.79]) by mx.google.com with ESMTP id oq7si26134352igc.64.2012.09.20.15.26.40; Thu, 20 Sep 2012 15:26:40 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 2016B2E088; Thu, 20 Sep 2012 22:26:40 +0000 (UTC) Received: from mail-iy0-f178.google.com (mail-iy0-f178.google.com [209.85.210.178]) by rubyforge.org (Postfix) with ESMTP id AABDE2E06C for ; Thu, 20 Sep 2012 22:26:11 +0000 (UTC) Received: by iaeh11 with SMTP id h11so2470825iae.23 for ; Thu, 20 Sep 2012 15:26:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:from:to:subject:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; bh=/4bFsvLQZwNnvdWxcmGGl19akqCcHRKZvobppMsH+i4=; b=ItWfswbHAjaiS1ontu08TWhH4/6l8dnTJ64M60aXglOsXxJ+7n1gsggxkWapMyEiYV EDDHnYtV1KNqP+bCRtUBzBz33yi2c9mVincTkS4neUqvcLGjtSMTiEish+/0B/O375mk gOSWHWBgzAexZGMnz/xI7yIr+EpoMsPTrHZRKplXApHJDBU6Mq5+AO35X6kuR+67wiSl qvjIxuANI0mupnciE9tjHHRLcZIZBcbRUm0xiMhaJfmIl/JX5wsb20gQfp+issmje9VP YvTHt1sUpEuEksaty/7VJvaaXIPfETrbzutxawXbTOoanuOrzaoQil8bHdW0O8PlD1ln qK1g== Received: by 10.50.195.234 with SMTP id ih10mr36654igc.21.1348179971205; Thu, 20 Sep 2012 15:26:11 -0700 (PDT) Received: from localhost ([64.56.231.94]) by mx.google.com with ESMTPS id fm8sm10109028igc.8.2012.09.20.15.26.08 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Sep 2012 15:26:10 -0700 (PDT) From: Steven Hum To: sup-talk In-reply-to: <1348123080-sup-7217@pruts.nl> References: <20120919211500.GH48050@armakuni.lastninja.net> <1348123080-sup-7217@pruts.nl> Date: Thu, 20 Sep 2012 18:25:23 -0400 Message-Id: <1348177473-sup-7941@monad> User-Agent: Sup/git Subject: Re: [sup-talk] any testimonials from users who transitioned from mutt? 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org I have used mutt with notmuch for ages and thought I would never switch until I came across sup recently. (notmuch, by the way is a very competent search mechanism - I believe there is even a mutt fork afoot to integrate it more seamlessly into mutt). sup does not back sync to maildir which for me should be a deal breaker as I like using offlineimap/imapfilter to maintain persistent mail on my desktop and laptop which allows me to peruse and respond to emails even when I am not connected to the Internet. Alas, I find sup so compelling a mail client that I am, for now, willing to put up with that serious lack. There are sup forks I have been looking into that appear to address this issue - but I am not sure if anyone is going to spearhead taking sup over officially to merge the work done in this area. The heliotrope/turnsole project is still not ready for prime time - beyond installation for me at least, the turnsole client crashes a lot. Even then, I am not sure if heliotrope will address the maildir back sync issue (there is an imaptrope fork which may address this). If it doesn't, it may not provide me with any benefit towards my offline mail usage. Like earlier posts, sup's tagging, smart conversation view (with only unread messages expanded - I am not sure if even Google's web gmail interface offers that) and facility to auto archive threads/folders/whatever rules you wish, just makes the email process more compelling and effective (for me) by eliminating inbox noise. The big back sync issue, however, does mean sup is non-destructive, so is worth a look if you are one of those people who is forever looking for the perfect email client (that sucks less :-) mutt will stay on my system if sup's maildir deficiency becomes intolerable - for now, I foresee using it to periodically prune and manage my maildirs. Steven -- "Truth or die." Steven Hum 5 - 28 Gilmour St Ottawa, ON K2P 0N3 email sdothum@gmail.com tel 613.237.9058 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk