On Wed, 10 Mar 2010 01:25:22 -0800, Carl Worth wrote:
> On Tue, 09 Mar 2010 16:19:16 -0400, David Bremner
> wrote:
> >
> > --format=tabular --output=message-id
>
> Ah, so maybe your "notmuch show --format=tabular" is basically the same
> thing I imagined for "notmuch search" (once we teach it
On Tue, 09 Mar 2010 16:19:16 -0400, David Bremner wrote:
> 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
Ah, so maybe your "notmuch
On Wed, 10 Mar 2010 01:25:22 -0800, Carl Worth cwo...@cworth.org wrote:
On Tue, 09 Mar 2010 16:19:16 -0400, David Bremner da...@tethera.net wrote:
--format=tabular --output=message-id
Ah, so maybe your notmuch show --format=tabular is basically the same
thing I imagined for notmuch
On Tue, 09 Mar 2010 11:51:46 -0800, Carl Worth 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
On Sat, 19 Dec 2009 10:55:24 -0400, david at tethera.net wrote:
> From: David Bremner
>
> Currently this only outputs the information from the "message header";
> i.e. the part before the rfc2822 header or body.
Hi David,
Are you proposing the tabular format for inclusion in notmuch?
Or does
On Sat, 19 Dec 2009 10:55:24 -0400, da...@tethera.net wrote:
From: David Bremner brem...@unb.ca
Currently this only outputs the information from the message header;
i.e. the part before the rfc2822 header or body.
Hi David,
Are you proposing the tabular format for inclusion in notmuch?
Or
From: David Bremner
Currently this only outputs the information from the "message header";
i.e. the part before the rfc2822 header or body.
Adding this required adding an extra parameter, currently unused, to
format_message_text and format_message_json. Also the struct
From: David Bremner brem...@unb.ca
Currently this only outputs the information from the message header;
i.e. the part before the rfc2822 header or body.
Adding this required adding an extra parameter, currently unused, to
format_message_text and format_message_json. Also the struct
definition is