From: Felipe Contreras <felipe.contreras@gmail.com>
To: Patrick Totzke <patricktotzke@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: the future of notmuch-vim?
Date: Wed, 3 Apr 2013 17:34:48 -0600 [thread overview]
Message-ID: <CAMP44s3GxHZMpECe=h3uBEhbY09c22+dctjeoVFuNEZUEfW63A@mail.gmail.com> (raw)
In-Reply-To: <20130403214846.11127.89080@brick.lan>
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
next prev parent reply other threads:[~2013-04-03 23:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 13:46 the future of notmuch-vim? David Bremner
2013-02-10 1:23 ` David Bremner
2013-02-16 12:23 ` David Bremner
2013-04-02 19:55 ` Felipe Contreras
2013-04-02 22:47 ` David Bremner
2013-04-03 6:01 ` guyzmo
2013-04-03 8:21 ` Patrick Totzke
2013-04-03 9:09 ` Felipe Contreras
2013-04-03 16:58 ` Suvayu Ali
2013-04-03 21:48 ` Patrick Totzke
2013-04-03 23:34 ` Felipe Contreras [this message]
2013-04-05 11:30 ` Charlie Allom
2013-06-03 0:48 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMP44s3GxHZMpECe=h3uBEhbY09c22+dctjeoVFuNEZUEfW63A@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=patricktotzke@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).