On Mon, 14 Dec 2009 14:30:45 -0800, Carl Worth wrote:
> I'm still not sure of the need to depend on a library just to *generate*
> any particular format. I would expect that job to be so constrained as
> to be almost trivial. I won't necessarily block a patch based on that,
> but I think we
On Sun, 13 Dec 2009 20:42:07 -0400, David Bremner wrote:
> On a different topic (and in response to Carl and your earlier
> discussion), as a counter-weight to the desire to avoid dependencies
> (which I agree with), I also think we should be careful about how many
> embedded copies of code there
On Sun, 13 Dec 2009 16:05:07 -0800, Scott Robinson
wrote:
> I have a patch for a --output=(text|json) for both notmuch-show and
> notmuch-search. I mentioned it earlier on the list, and no one seemed to have
> any interest.
Hi Scott,
I remember you mentioning this earlier, but I didn't
On Sun, 13 Dec 2009 19:21:02 -0400, David Bremner wrote:
> It would be nice to have more structured output from notmuch-show. I
> decided to investigate sexp (i.e. lisp) and json output.
Thanks, David!
> Then I found that json parsing is provided by the library json.el
> shipped with emacs23,
Excerpts from David Bremner's message of Mon Dec 14 00:21:02 +0100 2009:
> So, do people think this is a reasonable idea to persue?
JSON was actually the first thing I thought of when I first saw the
output of notmuch-show. I think it's a much more natural fit for notmuch
than say, sexps, since
On Sun, 13 Dec 2009 19:21:02 -0400, David Bremner da...@tethera.net wrote:
It would be nice to have more structured output from notmuch-show. I
decided to investigate sexp (i.e. lisp) and json output.
Thanks, David!
Then I found that json parsing is provided by the library json.el
shipped
On Sun, 13 Dec 2009 16:05:07 -0800, Scott Robinson sc...@quadhome.com wrote:
I have a patch for a --output=(text|json) for both notmuch-show and
notmuch-search. I mentioned it earlier on the list, and no one seemed to have
any interest.
Hi Scott,
I remember you mentioning this earlier, but I
On Sun, 13 Dec 2009 20:42:07 -0400, David Bremner brem...@unb.ca wrote:
On a different topic (and in response to Carl and your earlier
discussion), as a counter-weight to the desire to avoid dependencies
(which I agree with), I also think we should be careful about how many
embedded copies of
On Mon, 14 Dec 2009 14:30:45 -0800, Carl Worth cwo...@cworth.org wrote:
I'm still not sure of the need to depend on a library just to *generate*
any particular format. I would expect that job to be so constrained as
to be almost trivial. I won't necessarily block a patch based on that,
but I
On Sun, 13 Dec 2009 16:05:07 -0800, Scott Robinson
wrote:
> I have a patch for a --output=(text|json) for both notmuch-show and
> notmuch-search. I mentioned it earlier on the list, and no one seemed to have
> any interest.
Ahh, I missed that. I think it was just before I subscribed to the
On Sun, 13 Dec 2009 19:21:02 -0400, David Bremner wrote:
>
> Attachments: json output of a message from carl, and the equivalent
> sexpr as parsed by json.el.
>
uh, right. Second time lucky.
-- next part --
A non-text attachment was scrubbed...
Name: msg.json
Type:
It would be nice to have more structured output from notmuch-show. I
decided to investigate sexp (i.e. lisp) and json output.
Sexp has the obvious advantage that it is trivially parsable in emacs;
for other clients it is a little more work. I started looking at
sfsexp
Excerpts from David Bremner's message of Sun Dec 13 15:26:02 -0800 2009:
> On Sun, 13 Dec 2009 19:21:02 -0400, David Bremner
> wrote:
> >
> > Attachments: json output of a message from carl, and the equivalent
> > sexpr as parsed by json.el.
> >
> uh, right. Second time lucky.
>
I have a
It would be nice to have more structured output from notmuch-show. I
decided to investigate sexp (i.e. lisp) and json output.
Sexp has the obvious advantage that it is trivially parsable in emacs;
for other clients it is a little more work. I started looking at
sfsexp
On Sun, 13 Dec 2009 19:21:02 -0400, David Bremner da...@tethera.net wrote:
Attachments: json output of a message from carl, and the equivalent
sexpr as parsed by json.el.
uh, right. Second time lucky.
msg.json
Description: json encoded message
msg.sexpr
Description: msg converted to
Excerpts from David Bremner's message of Sun Dec 13 15:26:02 -0800 2009:
On Sun, 13 Dec 2009 19:21:02 -0400, David Bremner da...@tethera.net wrote:
Attachments: json output of a message from carl, and the equivalent
sexpr as parsed by json.el.
uh, right. Second time lucky.
I have
Excerpts from David Bremner's message of Mon Dec 14 00:21:02 +0100 2009:
So, do people think this is a reasonable idea to persue?
JSON was actually the first thing I thought of when I first saw the
output of notmuch-show. I think it's a much more natural fit for notmuch
than say, sexps, since
On Sun, 13 Dec 2009 16:05:07 -0800, Scott Robinson sc...@quadhome.com wrote:
I have a patch for a --output=(text|json) for both notmuch-show and
notmuch-search. I mentioned it earlier on the list, and no one seemed to have
any interest.
Ahh, I missed that. I think it was just before I
18 matches
Mail list logo
