Exporting a single email as JSON

2011-12-11 Thread Ciprian Dorin Craciun
On Sun, Dec 11, 2011 at 01:19, Jameson Graef Rollins wrote: > On Sun, 11 Dec 2011 00:46:51 +0200, Ciprian Dorin Craciun gmail.com> wrote: >> ? ? * in my use-case I would need each line of the output to be a >> standalone JSON object of an individual message; (thus I can script >> with Bash

Exporting a single email as JSON

2011-12-11 Thread Ciprian Dorin Craciun
On Sat, Dec 10, 2011 at 22:15, Jameson Graef Rollins wrote: > On Sat, 10 Dec 2011 20:32:22 +0200, Ciprian Dorin Craciun gmail.com> wrote: >> ? ? Quick question: why isn't it reasonable to export a **single** >> email in JSON format (by using the `show` sub-command)? (I mean I >> understand that

Exporting a single email as JSON

2011-12-10 Thread Austin Clements
Just to add to Jameson's email... Quoth Ciprian Dorin Craciun on Dec 11 at 12:46 am: > On Sat, Dec 10, 2011 at 22:15, Jameson Graef Rollins > wrote: > > On Sat, 10 Dec 2011 20:32:22 +0200, Ciprian Dorin Craciun > at gmail.com> wrote: > >> ? ? Quick question: why isn't it reasonable to export a

Exporting a single email as JSON

2011-12-10 Thread Ciprian Dorin Craciun
Hello all! Quick question: why isn't it reasonable to export a **single** email in JSON format (by using the `show` sub-command)? (I mean I understand that in order to be able to correctly parse the output we need only one "object" (i.e. a list of threads, containing a list of emails,

Exporting a single email as JSON

2011-12-10 Thread Jameson Graef Rollins
On Sun, 11 Dec 2011 00:46:51 +0200, Ciprian Dorin Craciun wrote: > I've given a quick look into `notmuch-show.c` (commit from > December 4) and indeed it seems quite trivial to add new formats. > > Thus I wonder: > a) Is the code suitable for experimenting such a feature? (I mean >

Exporting a single email as JSON

2011-12-10 Thread Jameson Graef Rollins
On Sat, 10 Dec 2011 20:32:22 +0200, Ciprian Dorin Craciun wrote: > Quick question: why isn't it reasonable to export a **single** > email in JSON format (by using the `show` sub-command)? (I mean I > understand that in order to be able to correctly parse the output we > need only one "object"

Re: Exporting a single email as JSON

2011-12-10 Thread Jameson Graef Rollins
On Sat, 10 Dec 2011 20:32:22 +0200, Ciprian Dorin Craciun ciprian.crac...@gmail.com wrote: Quick question: why isn't it reasonable to export a **single** email in JSON format (by using the `show` sub-command)? (I mean I understand that in order to be able to correctly parse the output we

Re: Exporting a single email as JSON

2011-12-10 Thread Ciprian Dorin Craciun
On Sat, Dec 10, 2011 at 22:15, Jameson Graef Rollins jroll...@finestructure.net wrote: On Sat, 10 Dec 2011 20:32:22 +0200, Ciprian Dorin Craciun ciprian.crac...@gmail.com wrote:     Quick question: why isn't it reasonable to export a **single** email in JSON format (by using the `show`

Re: Exporting a single email as JSON

2011-12-10 Thread Jameson Graef Rollins
On Sun, 11 Dec 2011 00:46:51 +0200, Ciprian Dorin Craciun ciprian.crac...@gmail.com wrote: I've given a quick look into `notmuch-show.c` (commit from December 4) and indeed it seems quite trivial to add new formats. Thus I wonder: a) Is the code suitable for experimenting such a

Re: Exporting a single email as JSON

2011-12-10 Thread Ciprian Dorin Craciun
On Sun, Dec 11, 2011 at 01:19, Jameson Graef Rollins jroll...@finestructure.net wrote: On Sun, 11 Dec 2011 00:46:51 +0200, Ciprian Dorin Craciun ciprian.crac...@gmail.com wrote:     * in my use-case I would need each line of the output to be a standalone JSON object of an individual message;

Re: Exporting a single email as JSON

2011-12-10 Thread Austin Clements
Just to add to Jameson's email... Quoth Ciprian Dorin Craciun on Dec 11 at 12:46 am: On Sat, Dec 10, 2011 at 22:15, Jameson Graef Rollins jroll...@finestructure.net wrote: On Sat, 10 Dec 2011 20:32:22 +0200, Ciprian Dorin Craciun ciprian.crac...@gmail.com wrote:     Quick question: why