From: David Bremner <david@tethera.net>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
In-Reply-To: <87r5nt8e99.fsf@yoom.home.cworth.org>
References: <87iqc4yyo8.fsf@yoom.home.cworth.org>
	<1261234524-25522-1-git-send-email-david@tethera.net>
	<1261234524-25522-2-git-send-email-david@tethera.net>
	<1261234524-25522-3-git-send-email-david@tethera.net>
	<1261234524-25522-4-git-send-email-david@tethera.net>
	<87r5nt8e99.fsf@yoom.home.cworth.org>
Date: Tue, 09 Mar 2010 16:19:16 -0400
Message-ID: <87iq95uu2j.fsf@convex-new.cs.unb.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] [PATCH 3/3] notmuch-show.c: prototype tabular output
 format, with output control
Precedence: list

On Tue, 09 Mar 2010 11:51:46 -0800, Carl Worth <cworth@cworth.org> wrote:

> Are you proposing the tabular format for inclusion in notmuch?
> 
> Or does "prototype" suggest that you were just showing a demonstration
> of what could be done here?
> 
> If you do want this included, what's the motivation for this format?

I think some tabular format would be handy because it is very easy to
parse with scripts, and because it is a natural natural way to get
e.g. a list of message-ids.

--format=tabular --output=message-id

On the other hand, I'm not yet using this code, so I guess the main
point is to discuss how output control should be implemented, and in
that sense the patch is a demo. I suspect once we start using json
output more, we will definitely want it there.

All the best, 

David