From: Felipe Contreras <felipe.contreras@gmail.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: RE: the future of notmuch-vim?
Date: Tue, 02 Apr 2013 13:55:13 -0600 [thread overview]
Message-ID: <515b37a1821fc_146e1045e1094149@nysa.mail> (raw)
In-Reply-To: <871udhcmks.fsf@zancas.localnet>
Hi,
Sorry for the late reply, I wasn't following the ml.
David Bremner wrote:
> There is apparently still some people that use it (although notice the
> "Vote" column is 0).
>
> On the other hand
>
> - The vim frontend is afaik the last thing depending on the legacy text
> output format.
>
> - The plugin seems to be only semi-functional at the moment; in a quick
> test I found a message that didn't display it's content, and one that
> displayed the content, along with "junk" from the internal
> representation.
Indeed, I'd say the code is very poor at best.
> - There are now several alternatives for people whose only motivation to
> use the vim frontend was dislike of emacs (alot and notmuch-mutt).
I did try the emacs frontend, and it was not working properly for me at the
time, and I believe I documented my issues. It was not just my dislike of emacs
that motivated me to write notmuch-vim-ruby.
> There are several alternative vim frontends floating around in (at
> least) ruby and python. I don't if they are better or worse
> functionality wise.
I'd say notmuch-vim-ruby is the best one, but of course I'm biased :)
> I'm considering stopping building debian packages for notmuch-vim, since
> I don't see any current prospects for the package improving. I'm not
> sure what the equivalent thing to do upstream would be, perhaps moving
> it to contrib. Or, deprecating it and then removing it.
>
> What do people think?
Personally I think notmuch-vim should be replaced with notmuch-vim-ruby. I did
try the python version, and remember discussing options with the guy developing
it, but nothing happened out of it, and I think the ruby version is superior.
I'd be open to discuss the options here, but I think notmuch-vim-ruby is the
only real option.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2013-04-02 20:03 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 [this message]
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
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=515b37a1821fc_146e1045e1094149@nysa.mail \
--to=felipe.contreras@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/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).