RE: the future of notmuch-vim?

diff --git a/4a/68335c2094565f9f7195a7ca4c94c6c7c9acb3 b/4a/68335c2094565f9f7195a7ca4c94c6c7c9acb3
new file mode 100644 (file)
index 0000000..fe5a3d2
--- /dev/null
+++ b/4a/68335c2094565f9f7195a7ca4c94c6c7c9acb3
@@ -0,0 +1,118 @@
+Return-Path: <felipe.contreras@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 8687A431FAF\r
+       for <notmuch@notmuchmail.org>; Tue,  2 Apr 2013 13:03:24 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id vh2v-yQhjKVD for <notmuch@notmuchmail.org>;\r
+       Tue,  2 Apr 2013 13:03:24 -0700 (PDT)\r
+Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com\r
+       [209.85.161.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 0750A431FAE\r
+       for <notmuch@notmuchmail.org>; Tue,  2 Apr 2013 13:03:23 -0700 (PDT)\r
+Received: by mail-gg0-f182.google.com with SMTP id u2so125550ggn.27\r
+       for <notmuch@notmuchmail.org>; Tue, 02 Apr 2013 13:03:23 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=x-received:date:from:to:cc:message-id:in-reply-to:references\r
+       :subject:mime-version:content-type:content-transfer-encoding;\r
+       bh=D6NHyt4H5BipW6FMv130x8fel/HgMD3hwna7mE60KiA=;\r
+       b=U4qFK21ZNzmWfok/ZhtVBB+dXZ9srXvhst5RS8VdmGL1pSGZ8CiKNhzylK3++GOlmD\r
+       bSN0I9nDm1DywTU7oKC59JB0qtUkp4twsW17hLLQ57208exbMMduoR+8XrNxwSmq9NA7\r
+       PZ9XyPRN+Orw4AeabPoqec4grWzZo4Js5xKgJaWhlweVwfjCgGeBlHIH7XXf7wtgv7g2\r
+       8O9Ppnq07yTdqLxW6rItD/UfEcjt7a/Hw4PJAoA4dGfVS7BEDpIGuZxjl8QQWes1fxLe\r
+       TTj1j+t34jHXNfDDmdDwOIHNUYx5EARfHpz73gYdGzqMJoradcIyMRUUfzfvrFcLcfv6\r
+       cFwA==\r
+X-Received: by 10.236.14.5 with SMTP id c5mr16230698yhc.194.1364933003525;\r
+       Tue, 02 Apr 2013 13:03:23 -0700 (PDT)\r
+Received: from localhost (187-163-100-70.static.axtel.net. [187.163.100.70])\r
+       by mx.google.com with ESMTPS id 30sm5211263yhb.6.2013.04.02.13.03.21\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Tue, 02 Apr 2013 13:03:22 -0700 (PDT)\r
+Date: Tue, 02 Apr 2013 13:55:13 -0600\r
+From: Felipe Contreras <felipe.contreras@gmail.com>\r
+To: David Bremner <david@tethera.net>, \r
+ notmuch@notmuchmail.org\r
+Message-ID: <515b37a1821fc_146e1045e1094149@nysa.mail>\r
+In-Reply-To: <871udhcmks.fsf@zancas.localnet>\r
+References: <871udhcmks.fsf@zancas.localnet>\r
+Subject: RE: the future of notmuch-vim?\r
+Mime-Version: 1.0\r
+Content-Type: text/plain;\r
+ charset=utf-8\r
+Content-Transfer-Encoding: 7bit\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 02 Apr 2013 20:03:24 -0000\r
+\r
+Hi,\r
+\r
+Sorry for the late reply, I wasn't following the ml.\r
+\r
+David Bremner wrote:\r
+\r
+> There is apparently still some people that use it (although notice the\r
+> "Vote" column is 0).\r
+> \r
+> On the other hand\r
+> \r
+> - The vim frontend is afaik the last thing depending on the legacy text\r
+>   output format.\r
+> \r
+> - The plugin seems to be only semi-functional at the moment; in a quick\r
+>   test I found a message that didn't display it's content, and one that\r
+>   displayed the content, along with "junk" from the internal\r
+>   representation.\r
+\r
+Indeed, I'd say the code is very poor at best.\r
+\r
+> - There are now several alternatives for people whose only motivation to\r
+>   use the vim frontend was dislike of emacs (alot and notmuch-mutt).\r
+\r
+I did try the emacs frontend, and it was not working properly for me at the\r
+time, and I believe I documented my issues. It was not just my dislike of emacs\r
+that motivated me to write notmuch-vim-ruby.\r
+\r
+> There are several alternative vim frontends floating around in (at\r
+> least) ruby and python. I don't if they are better or worse\r
+> functionality wise. \r
+\r
+I'd say notmuch-vim-ruby is the best one, but of course I'm biased :)\r
+\r
+> I'm considering stopping building debian packages for notmuch-vim, since\r
+> I don't see any current prospects for the package improving.  I'm not\r
+> sure what the equivalent thing to do upstream would be, perhaps moving\r
+> it to contrib. Or, deprecating it and then removing it.\r
+> \r
+> What do people think?\r
+\r
+Personally I think notmuch-vim should be replaced with notmuch-vim-ruby. I did\r
+try the python version, and remember discussing options with the guy developing\r
+it, but nothing happened out of it, and I think the ruby version is superior.\r
+\r
+I'd be open to discuss the options here, but I think notmuch-vim-ruby is the\r
+only real option.\r
+\r
+Cheers.\r
+\r
+-- \r
+Felipe Contreras\r