unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: notmuch@notmuchmail.org
Subject: Status of Vim client
Date: Thu, 29 Sep 2016 10:21:16 -0500	[thread overview]
Message-ID: <20160929152116.GB17434@tuna.imca.aps.anl.gov> (raw)

Hello, Notmuchers!

What is the status of the Vim client?  The last commit to
vim/notmuch.vim was over a year and a half ago (2015-01-23).

I'm also aware of two Vim clients on GitHub:

* https://github.com/felipec/notmuch-vim (last commit: 2014-05-22)

* https://github.com/imain/notmuch-vim (last commit: 2015-08-24)

So, are the clients really stable, or are they rotting because nobody
uses them?  My hope is the former, but I suspect the latter.  Are most
of the Vim people just using Mutt or NeoMutt?

Thanks!

Lewis

             reply	other threads:[~2016-09-29 15:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 15:21 J. Lewis Muir [this message]
2016-09-29 17:52 ` Status of Vim client Lucas Hoffmann
2016-09-29 18:52 ` David Bremner
2016-10-08  0:08 ` Nick Howell
2016-10-11  0:39   ` Nick Howell
2016-10-13 17:18     ` David Bremner
2016-10-13 18:19       ` nlhowell
2016-10-13 19:58         ` [RFC PATCH 0/2] vim: add "attach" support to compose Nick Howell
2016-10-13 19:58           ` [RFC PATCH 1/2] vim: compose: support additional Notmuch- filters Nick Howell
2016-10-13 19:58           ` [RFC PATCH 2/2] vim: compose: attachment support Nick Howell
2016-10-13 20:13         ` [RFC PATCH 0/7] vim: add mailcap filtering to show Nick Howell
2016-10-13 20:13           ` [RFC PATCH 1/7] vim: show: add mailcap filtering Nick Howell
2016-10-13 20:13           ` [RFC PATCH 2/7] vim: mailcap: forbid access to display server Nick Howell
2016-10-13 20:13           ` [RFC PATCH 3/7] vim: mailcap: gracefully handle missing mimetype Nick Howell
2016-10-13 20:13           ` [RFC PATCH 4/7] vim: mailcap: don't corrupt the view if filters write to stderr Nick Howell
2016-10-13 20:13           ` [RFC PATCH 5/7] vim: mailcap: redraw after processing Nick Howell
2016-10-13 20:13           ` [RFC PATCH 6/7] vim: mailcap: show all alternatives if none preferred Nick Howell
2016-10-13 20:13           ` [RFC PATCH 7/7] vim: mailcap: handle mailcap failure gracefully Nick Howell
2016-10-13 20:47           ` [RFC PATCHv2 0/8] vim: add mailcap filtering to show Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 1/8] vim: show: add mailcap filtering Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 2/8] vim: mailcap: forbid access to display server Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 3/8] vim: mailcap: gracefully handle missing mimetype Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 4/8] vim: mailcap: don't corrupt the view if filters write to stderr Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 5/8] vim: mailcap: redraw after processing Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 6/8] vim: show: add multipart/alternative picking Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 7/8] vim: mailcap: show all alternatives if none preferred Nick Howell
2016-10-13 20:47             ` [RFC PATCHv2 8/8] vim: mailcap: handle mailcap failure gracefully Nick Howell
2016-10-13 20:42         ` Status of Vim client David Bremner

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=20160929152116.GB17434@tuna.imca.aps.anl.gov \
    --to=jlmuir@imca-cat.org \
    --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).