From: Jameson Rollins <jrollins@finestructure.net>
To: racin@free.fr, Sebastian Spaeth <Sebastian@SSpaeth.de>
In-Reply-To:
 <74981806.5014941267021638774.JavaMail.root@zimbra1-e1.priv.proxad.net>
References:
 <74981806.5014941267021638774.JavaMail.root@zimbra1-e1.priv.proxad.net>
Date: Wed, 24 Feb 2010 09:56:09 -0500
Message-ID: <878wai3com.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Cc: notmuch@notmuchmail.org
Subject: Re: [notmuch] JSON output as default [was: Re: [PATCH] Add an
 "--output=(json|text|)" command-line option...]
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Wed, 24 Feb 2010 15:27:18 +0100 (CET), racin@free.fr wrote:
> > > 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.
> >=20
> > 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:
> >=20
> > notmuch show to:Diana --output=3Dto --sort=3Drelevance --limit=3D20
> >=20
> > just getting back a plain list of mail addresses is the easiest to
> > handle.
>=20
> 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 fiel=
ds in all messages in plain text
> separated by newlines (this is even easier to handle in emacs code than J=
SON). In fact, most of the C code I had
> to write for this patch is better replaced by the --output option...

Ok, I'm convinced.  I can see how they're both useful.  I had been
thinking more about the fact that text output isn't so useful for
multiline content (like message content), but I can see how it would be
useful for single line output.

I had also been thinking about the fact that the current "text" output,
specifically for the "show" command, *is* structured, but just not
according to any standard that I know of.  If the output is going to be
structured (ie. "show" output) then it should be in JSON format.  If
not, like the output of a single field that is a single line, then
having text output is definitely useful.

jamie.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLhT4KAAoJEO00zqvie6q8ecQP/RQkakG2wZzhPsP4TvKhaNqn
J8kwCHgKflf2JsGxHIhbkfwikGpad4OulaRFoTVmsVHcAhhCy2oF9jqeFO/vgNJE
aVFckPrOIpgappRKuXKqAO1HYcFGyJKyFu45LczgKtnrGaW2vmKRIy2+lEHbbHUW
TyBi8QOFP6z4WLyv+xow+kkph8itPtB8G/0X7aWSzqCxZWptjyG/q/XBCSg69//9
uKjQ2sUfVNNcqwKVayh2Fm7+KDMj48Im8pYhaymFocH0N8MB4iJtmsEioM7SPKGV
VcW0pv2YRJ5RwU/G81aaktqHN37H/5AbQKv3CFW3PRgHk7M0ux1hhVncUK2fv5ta
Fo7jsMz6gw+FUQ4zWzHNE+Z3vECkSKgZhAGQnCcExkod7UFQ+aBlWaY16AfRSVJ+
UPHX8EjpDnDqRINsLUJGEUcyId0LfQEGDmS/v+C3rudd3vhMb3lqMg42yEVIMMLT
MKwAPr0E7/LWYY4Ejxd4fQtZ/YA21fFO16Ekn5NXZwFnTU/53o2QaxIOvkYYpBKL
rLR5B5LOCJKOrz/GEpHz5XbBsT9aJYEm/7sn36NaC9l/oQ0/U7zc2M+u/HTRv1ll
LcgUDUye5k5VKfWDRHfU/Wk+OJ69yNvt/zrSxHmQaU2PLHITanQlgcBASqKWR4i7
+gUCzZ1d/ym5dVl79zIt
=IcAJ
-----END PGP SIGNATURE-----
--=-=-=--