From: David Bremner <david@tethera.net>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
In-Reply-To: <87iqc4yyo8.fsf@yoom.home.cworth.org>
References: <1261114167-sup-8228@lisa>
	<1261141195-5469-1-git-send-email-david@tethera.net>
	<87iqc4yyo8.fsf@yoom.home.cworth.org>
Date: Fri, 18 Dec 2009 20:36:34 -0400
Message-ID: <871virsstp.fsf@pivot.cs.unb.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] [PATCH] Add an "--output=(json|text|)" command-line
 option to both notmuch-search and notmuch-show.
Precedence: list

On Fri, 18 Dec 2009 09:33:43 -0800, Carl Worth <cworth@cworth.org> 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, 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 :).  Also, "search --for tags foo" suggests to me that
searching for tags matching foo.  What about using --output for that?
One thing that is not completely clear to me at this point is what the
difference is between 

    notmuch search --for messages  search-terms

and 

    notmuch show search-terms

David