From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 44F12431FBC for ; Thu, 25 Feb 2010 09:06:17 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.866 X-Spam-Level: X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5 tests=[AWL=-0.867, BAYES_50=0.001] autolearn=ham Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f7z+yM0EMlBE for ; Thu, 25 Feb 2010 09:06:16 -0800 (PST) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.190]) by olra.theworths.org (Postfix) with ESMTP id 63714431FAE for ; Thu, 25 Feb 2010 09:06:16 -0800 (PST) Received: by gv-out-0910.google.com with SMTP id r4so137884gve.25 for ; Thu, 25 Feb 2010 09:06:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=4wl0FQrr2eB7jHj0jLiEztwfXe+stBnTga9eHcweHOw=; b=xpwLklNsYLx3Z/zI0jYwEunMSvBSsH2tId5v1qwm7IY8ybWZX2suHEeHUGDqjz1rWJ Pn62PZoiyyjA7HFmKervOlcv7B2J7x1iv4RDjV3EQKoKL+mkZyPbZn8RlMsOeiL1s6h6 ypvy6qUWUzl3t0Jxdd1a0HcrBZl+YNsjiPSik= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=tVBRdwWEVB+jY2mxIBW8DfekcJMnEnbPBBxdEBE8IovvKtmRBT0tpyMQ4NKW2obaVA 8qIRvCwefe1v6NZgNP+78llgAHJ5jfs/3aEFcHfpXfkB4M6MWO2khIIrvcQLRuTn9bQz 4x9GFgKVtemEghkOmZDBTJAoEf9JQlM0JqVrk= Received: by 10.102.130.13 with SMTP id c13mr657546mud.17.1267117571866; Thu, 25 Feb 2010 09:06:11 -0800 (PST) Received: from localhost (p4FE5F385.dip.t-dialin.net [79.229.243.133]) by mx.google.com with ESMTPS id y37sm15486963mug.59.2010.02.25.09.06.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 25 Feb 2010 09:06:09 -0800 (PST) Date: Thu, 25 Feb 2010 18:03:30 +0100 From: Arian Kuschki To: Ben Gamari Message-ID: <20100225170330.GA12986@localhost> References: <20100219164924.GA17997@localhost> <1266684499-sup-8107@ben-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1266684499-sup-8107@ben-laptop> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: notmuch Subject: Re: vim client X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2010 17:06:17 -0000 On Sat 20, 12:34 -0500, Ben Gamari wrote: > 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. What is the problem that you are trying to solve with asynchronous sub process support that you cannot solve with things like ':!notmuch tag +sometag pattern &' or with using temp files and ":autoread" for views that need to be updated regularly? This is a genuine question, I am just not very knowledgeable about these technicalities. Do you think improved sub process support will ever be merged into mainline vim seeing that is somewhat against the vim philosophy (or isn't it?)? > and I would > far prefer to use notmuch from within vim than from another specialized > application. I agree. I talked to Bart, the creator of the vim client and he said he was planning to resume his work on it in April at the earliest. I would really like to see a usable client before that, and I don't think there is that much to do to make that happen really. There is lots of existing code we can use for things like json parsing and handling MIME stuff in the python standard libraries for example. If anybody wants to fork Bart's repo I would be happy to submit patches and test , but I lack the qualification to maintain a fork myself unfortunately.