DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=content-type:subject:from:to:in-reply-to:references:date:message-id
	:user-agent:content-transfer-encoding;
	b=cX+YjWHd4quSk6HDXPr3iGsSS8NXK4FPbmbZOJ6dMsXahCuCHITUXE2Yw5+SQLzzO/
	YyoCYgBo8pqN4jFumRWQJ3k8g1CvvtEvW+aVzhk7KjROE+nitOG/D5G5PBmdvDAl1k2G
	Qm1EQDOv56V7ND1IZZuZ+VlkdRr/eTapNI9oI=
Content-Type: text/plain; charset=UTF-8
From: Ben Gamari <bgamari@gmail.com>
To: notmuch <notmuch@notmuchmail.org>
In-reply-to: <87k4vd5fm9.fsf@yoom.home.cworth.org>
References: <1262078148-sup-7891@ben-laptop>
	<87k4vd5fm9.fsf@yoom.home.cworth.org>
Date: Wed, 20 Jan 2010 13:39:56 -0500
Message-Id: <1264012584-sup-7221@ben-laptop>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit
Subject: Re: [notmuch] SWIG (and particularly Python) bindings
Precedence: list

Excerpts from Carl Worth's message of Wed Jan 20 03:45:34 -0500 2010:
> Welcome to Notmuch!
> 
Thanks!

> > Notmuch looks excellent, although it appears that its current front-end
> > for my editor of choice (vim) is a little lacking in some ways
> > (operations involving a call to notmuch invariably lock up vi for the
> > duration of the operation).
> 
> Yes. The emacs mode was similarly crippled initially and fairly painful
> until we fixed that, (and quite nice afterwards).
> 
I can easily believe that. I've tried using the vim mode and quickly
gave up. I think I'm going to have to stick with sup until I've added
the appropriate subprocess support into vim. I have some half-completed
code, but still have a ways to go.

> > these are to be included in-tree, I would be curious to hear people have
> > to say about how we might integrate it into the sup build system.
> 
> I can't say much about integrating with the sup build system...
> 
Heh. My bad.

- Ben