> > 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:
>
> 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:D
On Wed, 24 Feb 2010 15:27:18 +0100 (CET), racin at 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.
> >
> > While I would love to see JSON (even by default), I agree
On Wed, 24 Feb 2010 15:27:18 +0100 (CET), ra...@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.
> >
> > While I would love to see JSON (even by default), I agree. I
> > 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:
>
> 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:D
Hey, Carl. I mentioned this is an email a while back
(id:87eil4ygar.fsf at servo.finestructure.net), but I want to bring it up
again now that you're looking at the JSON output stuff. I would like to
make the case for JSON being the one and only output format. Here's the
arguments:
* JSON is a v
On Tue, 23 Feb 2010 16:00:01 -0500, Jameson Rollins
wrote:
> Hey, Carl. I mentioned this is an email a while back
> (id:87eil4ygar@servo.finestructure.net), but I want to bring it up
> again now that you're looking at the JSON output stuff. I would like to
> make the case for JSON being the
On Tue, 23 Feb 2010 16:00:01 -0500, Jameson Rollins wrote:
> Hey, Carl. I mentioned this is an email a while back
> (id:87eil4ygar.fsf at servo.finestructure.net), but I want to bring it up
> again now that you're looking at the JSON output stuff. I would like to
> make the case for JSON being t
Hey, Carl. I mentioned this is an email a while back
(id:87eil4ygar@servo.finestructure.net), but I want to bring it up
again now that you're looking at the JSON output stuff. I would like to
make the case for JSON being the one and only output format. Here's the
arguments:
* JSON is a very
10 matches
Mail list logo