1 Return-Path: <felipe.contreras@gmail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id B9AA2431FBC
\r
6 for <notmuch@notmuchmail.org>; Fri, 4 May 2012 04:19:16 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id zbtrdb9ybQBF for <notmuch@notmuchmail.org>;
\r
17 Fri, 4 May 2012 04:19:16 -0700 (PDT)
\r
18 Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
\r
19 [209.85.212.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id DC811431FB6
\r
22 for <notmuch@notmuchmail.org>; Fri, 4 May 2012 04:19:15 -0700 (PDT)
\r
23 Received: by wibhn6 with SMTP id hn6so1031037wib.2
\r
24 for <notmuch@notmuchmail.org>; Fri, 04 May 2012 04:19:13 -0700 (PDT)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
26 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
\r
28 bh=YBRbLzLzu1CsOpeWYozy+BtGiOIQpfHL/keli/A0hiM=;
\r
29 b=c+TA0/PJ+cE8Y1shVGwMwNKwnNePFJkgf/AdeHd48JmCwNU6FVuJrNF/EyIQOEqksK
\r
30 7zu4q5fpUQzgSGk6dJLXV6ch4gDuKXkhWh2eoH5YRmK8hDt3nMET3PGFcfAvQcyrLTcD
\r
31 /MTAyDqGG72bmnWhd3D+t9aTC4WUMeOn2e6ZsNKEC+IZeBvJ3BTUzbENYdNgxZg5pr/e
\r
32 dTTdSEKT9IEdWYnst/N9gr93sINYThyalBD5NzZHlru8PQySwNMOXekvn7NuTF4t3E3O
\r
33 4asm3ygY6dq0+FdR9b1sAZVQXy810LjlGkQ3ryvkuVSVKPK+cqrrtcKeMYSVlPU2q7HX
\r
36 Received: by 10.216.225.12 with SMTP id y12mr3610391wep.39.1336130353045; Fri,
\r
37 04 May 2012 04:19:13 -0700 (PDT)
\r
38 Received: by 10.216.124.197 with HTTP; Fri, 4 May 2012 04:19:13 -0700 (PDT)
\r
39 In-Reply-To: <20120502202340.4214.21470@daenerys.khirnov.net>
\r
40 References: <20120114075443.27927.39754@daenerys.khirnov.net>
\r
41 <CAMP44s0h=RLNfcs-rLZofMVE88jgQ5KAnfsHNiK9snJi4ctmyw@mail.gmail.com>
\r
42 <CAMP44s26n0GgCf3nKawj52+aTFPFmPaA1K3sWLKSXv8KUcabOg@mail.gmail.com>
\r
43 <CAMP44s0dKJduJs=N-1OqMRZRGyB+GPQXWnbNwBnK0BH7RKxX_g@mail.gmail.com>
\r
44 <20120502202340.4214.21470@daenerys.khirnov.net>
\r
45 Date: Fri, 4 May 2012 13:19:13 +0200
\r
47 <CAMP44s1fpjF4uFP9BKtD32czk8B9NNfdFwa0Jf59Sx99ZiA7Cg@mail.gmail.com>
\r
48 Subject: Re: [RFC] vim plugin rewrite II
\r
49 From: Felipe Contreras <felipe.contreras@gmail.com>
\r
50 To: Anton Khirnov <anton@khirnov.net>
\r
51 Content-Type: text/plain; charset=UTF-8
\r
52 Cc: notmuch@notmuchmail.org
\r
53 X-BeenThere: notmuch@notmuchmail.org
\r
54 X-Mailman-Version: 2.1.13
\r
56 List-Id: "Use and development of the notmuch mail system."
\r
57 <notmuch.notmuchmail.org>
\r
58 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
60 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
61 List-Post: <mailto:notmuch@notmuchmail.org>
\r
62 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
63 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
65 X-List-Received-Date: Fri, 04 May 2012 11:19:16 -0000
\r
67 On Wed, May 2, 2012 at 10:23 PM, Anton Khirnov <anton@khirnov.net> wrote:
\r
69 > sorry for the late reply, I see you already reached the same point as
\r
70 > me, except with ruby ;) Yay for competition.
\r
72 I think my plugin is a bit further. And yeah, competition is good, but
\r
73 also collaboration; hopefully the 3 plugins can share as much as
\r
76 >> I was seriously considering to concentrate on this plugin instead of
\r
77 >> the current one, but I'm afraid every little error causes a crash,
\r
78 >> even when a subprocess fails (e.g. msmtp), so it's not really usable
\r
79 >> for me. Not to mention that it's really hard to debug, because every
\r
80 >> bug causes a crash, and sometimes I get random crashes with no
\r
81 >> information about what caused it at all.
\r
83 >> I am starting to work on a version that uses ruby, and it doesn't seem
\r
84 >> to have these issues, but lets see. I'm still not sure if we should
\r
85 >> depend on ruby/python bindings, maybe there's a way to make them
\r
88 >> Anyway, if you find a way to improve the crash issues, let me know, so
\r
89 >> far it's the only real issue I see with this plug-in.
\r
91 > That is weird, I'm not getting any crashes here. On any exception in the
\r
92 > python code it prints the backtrace and continues normally. I don't
\r
93 > think I've ever seen it actually crash (not counting my ultimately
\r
94 > unsuccessfull attempts at threading). I wonder what could cause this.
\r
96 Interesting. I would need to check that, but I don't have time right now =/
\r