MIME-Version: 1.0
In-Reply-To: <20130403214846.11127.89080@brick.lan>
References: <871udhcmks.fsf@zancas.localnet>
	<515b37a1821fc_146e1045e1094149@nysa.mail>
	<20130403060158.GJ7702@vilya.m0g.net>
	<515bf1d3cdb5b_79f845e181791@nysa.mail>
	<20130403214846.11127.89080@brick.lan>
Date: Wed, 3 Apr 2013 17:34:48 -0600
Message-ID:
 <CAMP44s3GxHZMpECe=h3uBEhbY09c22+dctjeoVFuNEZUEfW63A@mail.gmail.com>
Subject: Re: the future of notmuch-vim?
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Patrick Totzke <patricktotzke@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: notmuch@notmuchmail.org
Precedence: list

On Wed, Apr 3, 2013 at 3:48 PM, Patrick Totzke <patricktotzke@gmail.com> wrote:
> Quoting Felipe Contreras (2013-04-03 10:09:39)
>> ...
>> What you prefer is irrelevant; it's relevant only for you, that's why it's
>> called a *preference*, the rest of us prefer different things.
>
> Never mind preferences, I think originally, this thread was about dropping
> *support* for the *original* vim plugin that lives in notmuch/contrib.
> I think we can all agree that this is reasonable.

The reasons for dropping the original vim script are exactly the same
reasons why it should be replaced with the ruby version.

> This should not keep you from hacking on your script, hosting
> it whereever you like and support it.
> For me, one of the charms of notmuch is exactly this extensibility.

Bpth are "my" scripts. I'm supposed to be the maintainer of the vim
script and I have commit access.

-- 
Felipe Contreras