MIME-Version: 1.0
In-Reply-To: <20120502202340.4214.21470@daenerys.khirnov.net>
References: <20120114075443.27927.39754@daenerys.khirnov.net>
	<CAMP44s0h=RLNfcs-rLZofMVE88jgQ5KAnfsHNiK9snJi4ctmyw@mail.gmail.com>
	<CAMP44s26n0GgCf3nKawj52+aTFPFmPaA1K3sWLKSXv8KUcabOg@mail.gmail.com>
	<CAMP44s0dKJduJs=N-1OqMRZRGyB+GPQXWnbNwBnK0BH7RKxX_g@mail.gmail.com>
	<20120502202340.4214.21470@daenerys.khirnov.net>
Date: Fri, 4 May 2012 13:19:13 +0200
Message-ID:
 <CAMP44s1fpjF4uFP9BKtD32czk8B9NNfdFwa0Jf59Sx99ZiA7Cg@mail.gmail.com>
Subject: Re: [RFC] vim plugin rewrite II
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Anton Khirnov <anton@khirnov.net>
Content-Type: text/plain; charset=UTF-8
Cc: notmuch@notmuchmail.org
Precedence: list

On Wed, May 2, 2012 at 10:23 PM, Anton Khirnov <anton@khirnov.net> wrote:

> sorry for the late reply, I see you already reached the same point as
> me, except with ruby ;) Yay for competition.

I think my plugin is a bit further. And yeah, competition is good, but
also collaboration; hopefully the 3 plugins can share as much as
possible.

>> I was seriously considering to concentrate on this plugin instead of
>> the current one, but I'm afraid every little error causes a crash,
>> even when a subprocess fails (e.g. msmtp), so it's not really usable
>> for me. Not to mention that it's really hard to debug, because every
>> bug causes a crash, and sometimes I get random crashes with no
>> information about what caused it at all.
>>
>> I am starting to work on a version that uses ruby, and it doesn't seem
>> to have these issues, but lets see. I'm still not sure if we should
>> depend on ruby/python bindings, maybe there's a way to make them
>> optional.
>>
>> Anyway, if you find a way to improve the crash issues, let me know, so
>> far it's the only real issue I see with this plug-in.
>
> That is weird, I'm not getting any crashes here. On any exception in the
> python code it prints the backtrace and continues normally. I don't
> think I've ever seen it actually crash (not counting my ultimately
> unsuccessfull attempts at threading). I wonder what could cause this.

Interesting. I would need to check that, but I don't have time right now =/

Cheers.

-- 
Felipe Contreras