unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Austin Clements <amdragon@MIT.EDU>
To: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v6 06/10] schemata: Add documentation for JSON reply format.
Date: Sun, 11 Mar 2012 20:36:13 -0400	[thread overview]
Message-ID: <20120312003613.GB2754@mit.edu> (raw)
In-Reply-To: <1329893199-21630-7-git-send-email-awg+notmuch@xvx.ca>

Oops.  Looks like I left references to various old JSON functions in
the schemata file.  I'll submit a patch to fix those up, but you might
as well use the correct function names in the new documentation.

Quoth Adam Wolfe Gordon on Feb 21 at 11:46 pm:
> ---
>  devel/schemata |   27 +++++++++++++++++++++++++--
>  1 files changed, 25 insertions(+), 2 deletions(-)
> 
> diff --git a/devel/schemata b/devel/schemata
> index d90d4c6..ee8cfc0 100644
> --- a/devel/schemata
> +++ b/devel/schemata
> @@ -74,8 +74,9 @@ part = {
>      content?:       string    # pre-fetched body content
>  }
>  
> -# The headers of a message (format_headers_json with raw headers) or
> -# a part (format_headers_message_part_json with pretty-printed headers)
> +# The headers of a message (format_headers_json with raw headers
> +# and reply = FALSE) or a part (format_headers_message_part_json
> +# with pretty-printed headers)

There's only format_headers_json now and it outputs pretty-printed
headers.

>  headers = {
>      Subject:        string,
>      From:           string,
> @@ -133,3 +134,25 @@ thread = {
>                                # matched and unmatched
>      subject:        string
>  }
> +
> +notmuch reply schema
> +--------------------
> +
> +reply = {
> +    # The headers of the constructed reply (format_headers_json with
> +    # raw headers and reply = TRUE)
> +    reply-headers: reply_headers,
> +
> +    # As in the show format (format_message_json)

format_part_json

> +    original: message
> +}
> +
> +reply_headers = {
> +    Subject:        string,
> +    From:           string,
> +    To?:            string,
> +    Cc?:            string,
> +    Bcc?:           string,
> +    In-reply-to:    string,
> +    References:     string
> +}

  reply	other threads:[~2012-03-12  0:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22  6:46 [PATCH v6 00/10] Reply improvements Adam Wolfe Gordon
2012-02-22  6:46 ` [PATCH v6 01/10] test: Add broken test for the new JSON reply format Adam Wolfe Gordon
2012-02-22  6:46 ` [PATCH v6 02/10] reply: Factor out reply creation Adam Wolfe Gordon
2012-03-08 22:05   ` Jani Nikula
2012-02-22  6:46 ` [PATCH v6 03/10] reply: Require that only one message is returned Adam Wolfe Gordon
2012-03-09 23:00   ` Jani Nikula
2012-03-10 18:29     ` Adam Wolfe Gordon
2012-03-12  0:29     ` Austin Clements
2012-02-22  6:46 ` [PATCH v6 04/10] TODO: Add replying to multiple messages Adam Wolfe Gordon
2012-02-22  6:46 ` [PATCH v6 05/10] reply: Add a JSON reply format Adam Wolfe Gordon
2012-03-09 23:08   ` Jani Nikula
2012-03-10 18:27     ` Adam Wolfe Gordon
2012-02-22  6:46 ` [PATCH v6 06/10] schemata: Add documentation for " Adam Wolfe Gordon
2012-03-12  0:36   ` Austin Clements [this message]
2012-03-12  4:09     ` Adam Wolfe Gordon
2012-03-12 20:57       ` Austin Clements
2012-02-22  6:46 ` [PATCH v6 07/10] man: Update notmuch-reply man page for JSON format Adam Wolfe Gordon
2012-02-22  6:46 ` [PATCH v6 08/10] emacs: Factor out useful functions into notmuch-lib Adam Wolfe Gordon
2012-02-22  6:46 ` [PATCH v6 09/10] test: Add broken tests for new emacs reply functionality Adam Wolfe Gordon
2012-02-22  6:46 ` [PATCH v6] emacs: Use the new JSON reply format and message-cite-original Adam Wolfe Gordon
2012-03-09 23:13   ` Jani Nikula
2012-03-10 18:19     ` Adam Wolfe Gordon
2012-03-12  1:11   ` Austin Clements
2012-02-25 21:29 ` [PATCH v6 00/10] Reply improvements David Bremner
2012-02-25 22:25   ` Adam Wolfe Gordon
2012-02-26  0:23     ` Austin Clements

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=20120312003613.GB2754@mit.edu \
    --to=amdragon@mit.edu \
    --cc=awg+notmuch@xvx.ca \
    --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).