unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Ben Gamari <bgamari@gmail.com>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: vim client
Date: Sat, 20 Feb 2010 12:34:00 -0500	[thread overview]
Message-ID: <1266684499-sup-8107@ben-laptop> (raw)
In-Reply-To: <20100219164924.GA17997@localhost>

Excerpts from Arian Kuschki's message of Fri Feb 19 11:49:25 -0500 2010:
> Hi all
> thank you for notmuch, it is a great project. I have been watching 
> progress for a while but then I could no longer restrain myself and 
> started using notmuch's vim client even though it is still a bit rough 
> around the edges. Unfortunately there are some quirks that 
> prevent me from switching over completely. 
> questions:
> 
> 1. will there be a usable  ncurses or mutt version that supports notmuch 
> anytime soon?

Not that I know of. I've thought of starting something before. I really
want to start using notmuch full-time myself, but I agree, the vim
client is far from usable.

> 2. is anybody working on the vim client? I have a small patch and might 
> have couple more as time passes. Is this mailing list the right place to 
> discuss this? From what I can gather the discussion seems to be centred 
> mainly on the emacs client.

I don't believe there is anyone working actively on the vim frontend at
the moment. I looked at it not so long ago and the code is pretty good.
The real problem is all notmuch calls are synchronous. Vim unfortunately
lacks the excellent asynchronous subprocess interface that emacs has.
Therefore, I'm afraid the vim client is going to be just as unuable
until someone has implemented asynchronous subprocess support.

I have a tree starting this sitting around somewhere, but it still has a
ways to go and I won't have time to finish until midterms are over at
the earliest. If someone else wants to take a stab at it, the code is
available git://goldnerlab.physics.umass.edu/vim7.git (the async-process
branch). I'd love to know if anyone makes any progress and I'll keep you
all in the loop if I find any time to invest in it.

I have considered starting work on an ncurses frontend, but I think
ultimately that time would be better used in working on the async vim
code. Vim gives us a whole lot of functionality for free that would take
time to get working on a new ncurses client (e.g. windowing) and I would
far prefer to use notmuch from within vim than from another specialized
application.

Cheers,

- Ben

  parent reply	other threads:[~2010-02-20 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 16:49 vim client Arian Kuschki
2010-02-19 20:12 ` Ruben Pollan
2010-02-21  6:56   ` notmuch for mutt (was: vim client) martin f krafft
2010-02-21 11:42     ` Ruben Pollan
2010-02-20 17:34 ` Ben Gamari [this message]
2010-02-25 17:03   ` vim client Arian Kuschki
2010-02-26  3:04     ` Ben Gamari

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=1266684499-sup-8107@ben-laptop \
    --to=bgamari@gmail.com \
    --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).