Date: Wed, 24 Feb 2010 15:27:18 +0100 (CET)
From: racin@free.fr
To: Sebastian Spaeth <Sebastian@SSpaeth.de>
Message-ID:
 <74981806.5014941267021638774.JavaMail.root@zimbra1-e1.priv.proxad.net>
In-Reply-To:
 <1257161639.5014171267021461605.JavaMail.root@zimbra1-e1.priv.proxad.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: notmuch@notmuchmail.org
Subject: Re: [notmuch] JSON output as default [was: Re: [PATCH] Add an
 "--output=(json|text|)" command-line option...]
Precedence: list


> > I definitely want to be able to pipe single-field lists coming from
> > notmuch to grep, xargs, shell for loops, etc. without having to
> decode
> > JSON.
> 
> While I would love to see JSON (even by default), I agree. If I just
> want to code up a notmuch-based address book with sth like:
> 
> notmuch show to:Diana --output=to --sort=relevance --limit=20
> 
> just getting back a plain list of mail addresses is the easiest to
> handle.

This would also be useful for the Emacs/Vim interfaces. For instance, my smart completion patch
would really benefit from notmuch being capable of outputing various fields in all messages in plain text
separated by newlines (this is even easier to handle in emacs code than JSON). In fact, most of the C code I had
to write for this patch is better replaced by the --output option...