From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Peter Feigl <craven@gmx.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] rewriting notmuch-search for structured output to make other output formats easier
Date: Sat, 21 Jan 2012 15:12:57 -0800 [thread overview]
Message-ID: <87k44klkee.fsf@servo.finestructure.net> (raw)
In-Reply-To: <1327180568-30385-1-git-send-email-craven@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Sat, 21 Jan 2012 22:16:08 +0100, Peter Feigl <craven@gmx.net> wrote:
> The output routines have been rewritten so that logical structure
> (objects with key/value pairs, arrays, strings and numbers) are
> written instead of ad-hoc printfs. This allows for easier adaptation
> of other output formats, as only the routines that start/end an object
> etc. have to be rewritten. The logic is the same for all formats.
> The default text output is handled differently, special cases are
> inserted at the proper places, as it differs too much from the
> structured output.
Hi, Peter. Thanks for the contribution.
There are a lot of changes in this patch so I think you need to think
about how you can break this up into multiple smaller and more atomic
patches. In particular, the addition of the sexp output format needs to
definitely be in a separate patch from the restructuring of the output
formatting. You also don't mention anywhere in the commit log that
you've added this new output format. You'll also need to include
documentation and test suite updates.
Thanks.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-01-21 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 21:16 [PATCH] rewriting notmuch-search for structured output to make other output formats easier Peter Feigl
2012-01-21 22:04 ` Austin Clements
2012-01-21 23:17 ` Peter Feigl
2012-01-22 0:23 ` Austin Clements
2012-01-21 23:12 ` Jameson Graef Rollins [this message]
2012-01-21 23:21 ` Peter Feigl
2012-01-22 0:34 ` Jameson Graef Rollins
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=87k44klkee.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=craven@gmx.net \
--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).