Content-Type: text/plain; charset=UTF-8
From: Scott Robinson <scott@quadhome.com>
To: notmuch <notmuch@notmuchmail.org>
In-reply-to: <87mxzhjj0s.fsf@rocinante.cs.unb.ca>
References: <id:1262249616-sup-3911@elise>
	<1262272660-16786-1-git-send-email-david@tethera.net>
	<87mxzhjj0s.fsf@rocinante.cs.unb.ca>
Date: Wed, 10 Feb 2010 11:54:45 -0600
Message-Id: <1265824234-sup-8219@elise>
User-Agent: Sup/0.10.2
Content-Transfer-Encoding: 8bit
Subject: Re: [notmuch] [PATCH] Add an "--format=(json|text)" command-line
	option to both notmuch-search and notmuch-show.
Precedence: list

Excerpts from David Bremner's message of Wed Feb 10 07:51:47 -0600 2010:
> Dear Scott and other interested parties;
> 
> As I play with json output a bit more, it seems like having
> --entire-thread optional would be useful for quite a few applications.
> For example, if I want to get the From address for a given message-ID, I
> with the current setup I have to post process the output. This is
> doable, but I wonder if the better option isn't to make --entire-thread
> optional for --format=json as well. 
> 
> Any thoughts?

I made --entire-thread forced becuase it kept the JSON patch minimal. The way
the thread structure is calculated is closely tied into the message tree
recursion. It would have required a much more significant refactoring to get
both ways; and, I wanted the patch to have as few barriers to being merged.

However, as patch still hasn't been merged and probably needs to be rebased,
there doesn't seem to be any good reason anymore to avoid the work.

Except, I can't do it. As I noted in an earlier e-mail, I have to abandon this
piece of code. I'm a bit busy backpacking through Central America. :-)