From: Scott Robinson <scott@quadhome.com>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Add an "--format=(json|text)" command-line option to both notmuch-search and notmuch-show.
Date: Wed, 10 Feb 2010 11:54:45 -0600 [thread overview]
Message-ID: <1265824234-sup-8219@elise> (raw)
In-Reply-To: <87mxzhjj0s.fsf@rocinante.cs.unb.ca>
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. :-)
next prev parent reply other threads:[~2010-02-10 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <id:1262249616-sup-3911@elise>
2009-12-31 15:17 ` [PATCH] Add an "--format=(json|text)" command-line option to both notmuch-search and notmuch-show david
2009-12-31 20:27 ` Scott Robinson
2010-02-10 13:51 ` David Bremner
2010-02-10 17:54 ` Scott Robinson [this message]
2010-02-23 20:56 ` Carl Worth
2010-03-01 14:58 ` [Sebastian Spaeth] " Sebastian Spaeth
2010-03-01 15:39 ` [PATCH] notmuch-show: add tags to json output Sebastian Spaeth
2010-03-01 17:26 ` David Bremner
2010-03-01 17:35 ` Jameson Rollins
2010-03-02 10:52 ` [PATCH 1/2] notmuch-show: Do not output (null) when the message body is empty Sebastian Spaeth
2010-03-02 10:52 ` [PATCH 2/2] notmuch-show: add tags to json output Sebastian Spaeth
2010-03-10 9:41 ` Sebastian Spaeth
2010-03-11 12:11 ` [PATCH] " Sebastian Spaeth
2010-03-11 12:34 ` Carl Worth
2010-03-01 15:59 ` more json woes Sebastian Spaeth
2010-03-01 16:12 ` [PATCH] notmuch-show: Do not output (null) when the message body is empty Sebastian Spaeth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1265824234-sup-8219@elise \
--to=scott@quadhome.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).