On Fri, 18 Dec 2009 08:59:55 -0400, david at tethera.net wrote:
> From: Scott Robinson
Hi Scott (and David),
I'm finally getting around to looking closely at the JSON patches
(hurrah!). Here are some comments:
> In the case of notmuch-show, "--output=json" also implies
> "--entire-thread" as
On Fri, 18 Dec 2009 20:36:34 -0400, David Bremner wrote:
> It's a detail, but could you choose two names that are not substrings of
> each other? Eventually we do want tab completion on the command line to
> work :).
Yes, that's a good point.
> Also, "search --for tags foo" suggests to me that
On Fri, 18 Dec 2009 09:33:43 -0800, Carl Worth wrote:
> I think that selecting *what* to emit is orthogonal from selecting *how*
> to format that output.
I can see that point of view.
> See some ideas in the TODO file, (where I proposed --for and --format
> options for these).
It's a detail,
Excerpts from Carl Worth's message of Fri Dec 18 09:33:43 -0800 2009:
> On Fri, 18 Dec 2009 08:59:55 -0400, david at tethera.net wrote:
> > It took me a little work to apply Scott's patch, so rather than asking
> > him to resend it from git-send-email, I am just sending. I hope no-one
> > is
On Fri, 18 Dec 2009 08:59:55 -0400, david at tethera.net wrote:
> It took me a little work to apply Scott's patch, so rather than asking
> him to resend it from git-send-email, I am just sending. I hope no-one
> is offended (much).
I think that's great! Collaboration is what this is all about.
>
From: Scott Robinson
In the case of notmuch-show, "--output=json" also implies
"--entire-thread" as the thread structure is implicit in the emitted
document tree.
As a coincidence to the implementation, multipart message ID numbers are
now incremented with each part printed.
On Fri, 18 Dec 2009 08:59:55 -0400, da...@tethera.net wrote:
It took me a little work to apply Scott's patch, so rather than asking
him to resend it from git-send-email, I am just sending. I hope no-one
is offended (much).
I think that's great! Collaboration is what this is all about.
I'm