From: Austin Clements <amdragon@MIT.EDU>
To: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v5.2 3/7] reply: Add a JSON reply format.
Date: Fri, 17 Feb 2012 12:04:57 -0500 [thread overview]
Message-ID: <20120217170457.GE5991@mit.edu> (raw)
In-Reply-To: <1329361957-28493-4-git-send-email-awg+notmuch@xvx.ca>
The first two patches LGTM. A few nits in this one.
Quoth Adam Wolfe Gordon on Feb 15 at 8:12 pm:
> This new JSON format for replies includes headers generated for a
> reply message as well as the headers of the original message. Using
> this data, a client can intelligently create a reply. For example, the
> emacs client will be able to create replies with quoted HTML parts by
> parsing the HTML parts.
>
> Reply now enforces that only one message is returned, as the semantics
> of replying to multiple messages are not well-defined.
> ---
> notmuch-client.h | 3 +
> notmuch-reply.c | 121 ++++++++++++++++++++++++++++++++++++++++++++++-------
> notmuch-show.c | 2 +-
> 3 files changed, 109 insertions(+), 17 deletions(-)
>
> diff --git a/notmuch-client.h b/notmuch-client.h
> index 60828aa..d28ea07 100644
> --- a/notmuch-client.h
> +++ b/notmuch-client.h
> @@ -344,6 +344,9 @@ typedef struct mime_node {
> int next_part_num;
> } mime_node_t;
>
> +void
> +format_part_json (const void *ctx, mime_node_t *node, notmuch_bool_t first);
> +
This is the wrong place for this declaration, since it is not part of
the MIME node abstraction. It should go somewhere above the /*
notmuch-config.c */ comment. Above that, it's a bit of a jumble. I'd
probably put it right after notmuch_show_command.
> /* Construct a new MIME node pointing to the root message part of
> * message. If cryptoctx is non-NULL, it will be used to verify
> * signatures on any child parts. If decrypt is true, then cryptoctx
> diff --git a/notmuch-reply.c b/notmuch-reply.c
> index 8e56245..6670288 100644
> --- a/notmuch-reply.c
> +++ b/notmuch-reply.c
> @@ -572,30 +572,115 @@ notmuch_reply_format_default(void *ctx,
> notmuch_message_t *message;
> const notmuch_show_format_t *format = &format_reply;
>
> - for (messages = notmuch_query_search_messages (query);
> - notmuch_messages_valid (messages);
> - notmuch_messages_move_to_next (messages))
> - {
> - message = notmuch_messages_get (messages);
> + if (notmuch_query_count_messages (query) != 1) {
> + fprintf (stderr, "Error: search term did not match precisely one message.\n");
> + return 1;
> + }
Technically count_messages does not have to be accurate, but since
this is the same thing notmuch-show does, it's probably fine for now.
Perhaps we should add proper handling of multi-message replies to
devel/TODO?
>
> - reply = create_reply_message (ctx, config, message, reply_all);
> + messages = notmuch_query_search_messages (query);
> + message = notmuch_messages_get (messages);
>
> - if (!reply)
> - continue;
> + reply = create_reply_message (ctx, config, message, reply_all);
>
> - show_reply_headers (reply);
> + if (!reply)
> + return 1;
>
> - g_object_unref (G_OBJECT (reply));
> - reply = NULL;
> + show_reply_headers (reply);
>
> - printf ("On %s, %s wrote:\n",
> - notmuch_message_get_header (message, "date"),
> - notmuch_message_get_header (message, "from"));
> + g_object_unref (G_OBJECT (reply));
> + reply = NULL;
>
> - show_message_body (message, format, params);
> + printf ("On %s, %s wrote:\n",
> + notmuch_message_get_header (message, "date"),
> + notmuch_message_get_header (message, "from"));
>
> - notmuch_message_destroy (message);
> + show_message_body (message, format, params);
> +
> + notmuch_message_destroy (message);
> +
> + return 0;
> +}
The above change could be separated out in to a separate patch, since
it has nothing to do with JSON.
> +
> +static void
> +format_reply_headers_json (const void *ctx, GMimeMessage *message)
> +{
> + void *local = talloc_new (ctx);
> + InternetAddressList *recipients;
> + const char *recipients_string;
> +
> + printf ("{%s: %s",
> + json_quote_str (local, "Subject"),
> + json_quote_str (local, g_mime_message_get_subject (message)));
> + printf (", %s: %s",
> + json_quote_str (local, "From"),
> + json_quote_str (local, g_mime_message_get_sender (message)));
> + recipients = g_mime_message_get_recipients (message, GMIME_RECIPIENT_TYPE_TO);
> + recipients_string = internet_address_list_to_string (recipients, 0);
> + if (recipients_string)
> + printf (", %s: %s",
> + json_quote_str (local, "To"),
> + json_quote_str (local, recipients_string));
> + recipients = g_mime_message_get_recipients (message, GMIME_RECIPIENT_TYPE_CC);
> + recipients_string = internet_address_list_to_string (recipients, 0);
> + if (recipients_string)
> + printf (", %s: %s",
> + json_quote_str (local, "Cc"),
> + json_quote_str (local, recipients_string));
> +
> + printf (", %s: %s",
> + json_quote_str (local, "In-reply-to"),
> + json_quote_str (local, g_mime_object_get_header (GMIME_OBJECT (message), "In-reply-to")));
> +
> + printf (", %s: %s",
There should be a close brace in this string, rather than opening the
object in this function and closing it in the caller.
> + json_quote_str (local, "References"),
> + json_quote_str (local, g_mime_object_get_header (GMIME_OBJECT (message), "References")));
> +
> + talloc_free (local);
> +}
I would much rather see format_headers_json in notmuch-show.c gain a
parameter that tells it whether or not to include in-reply-to and
references.
> +
> +static int
> +notmuch_reply_format_json(void *ctx,
> + notmuch_config_t *config,
> + notmuch_query_t *query,
> + notmuch_show_params_t *params,
> + notmuch_bool_t reply_all)
> +{
> + GMimeMessage *reply;
> + notmuch_messages_t *messages;
> + notmuch_message_t *message;
> + mime_node_t *node;
> +
> + if (notmuch_query_count_messages (query) != 1) {
> + fprintf (stderr, "Error: search term did not match precisely one message.\n");
> + return 1;
> }
> +
> + messages = notmuch_query_search_messages (query);
> + message = notmuch_messages_get (messages);
> + if (mime_node_open (ctx, message, params->cryptoctx, params->decrypt,
> + &node) != NOTMUCH_STATUS_SUCCESS)
> + return 1;
> +
> + reply = create_reply_message (ctx, config, message, reply_all);
> + if (!reply)
> + return 1;
> +
> + /* The headers of the reply message we've created */
> + printf ("{\"reply-headers\": ");
> + format_reply_headers_json (ctx, reply);
> + printf ("}");
> + g_object_unref (G_OBJECT (reply));
> + reply = NULL;
> +
> + /* Start the original */
> + printf (", \"original\": ");
> +
> + format_part_json (ctx, node, TRUE);
> +
> + /* End */
> + printf ("}\n");
> + notmuch_message_destroy (message);
> +
> return 0;
> }
>
> @@ -661,6 +746,7 @@ notmuch_reply_format_headers_only(void *ctx,
>
> enum {
> FORMAT_DEFAULT,
> + FORMAT_JSON,
> FORMAT_HEADERS_ONLY,
> };
>
> @@ -680,6 +766,7 @@ notmuch_reply_command (void *ctx, int argc, char *argv[])
> notmuch_opt_desc_t options[] = {
> { NOTMUCH_OPT_KEYWORD, &format, "format", 'f',
> (notmuch_keyword_t []){ { "default", FORMAT_DEFAULT },
> + { "json", FORMAT_JSON },
> { "headers-only", FORMAT_HEADERS_ONLY },
> { 0, 0 } } },
> { NOTMUCH_OPT_KEYWORD, &reply_all, "reply-to", 'r',
> @@ -698,6 +785,8 @@ notmuch_reply_command (void *ctx, int argc, char *argv[])
>
> if (format == FORMAT_HEADERS_ONLY)
> reply_format_func = notmuch_reply_format_headers_only;
> + else if (format == FORMAT_JSON)
> + reply_format_func = notmuch_reply_format_json;
> else
> reply_format_func = notmuch_reply_format_default;
>
> diff --git a/notmuch-show.c b/notmuch-show.c
> index 6a171a4..c570a16 100644
> --- a/notmuch-show.c
> +++ b/notmuch-show.c
> @@ -652,7 +652,7 @@ format_part_text (const void *ctx, mime_node_t *node,
> printf ("\f%s}\n", part_type);
> }
>
> -static void
> +void
> format_part_json (const void *ctx, mime_node_t *node, notmuch_bool_t first)
> {
> /* Any changes to the JSON format should be reflected in the file
next prev parent reply other threads:[~2012-02-17 17:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 3:12 [PATCH v5.2 0/7] Reply enhancements, tidied up Adam Wolfe Gordon
2012-02-16 3:12 ` [PATCH v5.2 1/7] test: Add broken test for the new JSON reply format Adam Wolfe Gordon
2012-02-17 18:20 ` Austin Clements
2012-02-16 3:12 ` [PATCH v5.2 2/7] reply: Factor out reply creation Adam Wolfe Gordon
2012-02-16 3:12 ` [PATCH v5.2 3/7] reply: Add a JSON reply format Adam Wolfe Gordon
2012-02-17 17:04 ` Austin Clements [this message]
2012-02-18 2:06 ` Adam Wolfe Gordon
2012-02-18 3:23 ` Austin Clements
2012-02-16 3:12 ` [PATCH v5.2 4/7] man: Update notmuch-reply man page for JSON format Adam Wolfe Gordon
2012-02-17 20:01 ` Austin Clements
2012-02-16 3:12 ` [PATCH v5.2 5/7] emacs: Factor out useful functions into notmuch-lib Adam Wolfe Gordon
2012-02-16 3:12 ` [PATCH v5.2 6/7] test: Add broken tests for new emacs reply functionality Adam Wolfe Gordon
2012-02-16 3:12 ` [PATCH v5.2 7/7] emacs: Use the new JSON reply format and message-cite-original Adam Wolfe Gordon
2012-02-17 20:00 ` Austin Clements
2012-02-18 2:22 ` Adam Wolfe Gordon
2012-02-18 3:30 ` Austin Clements
2012-02-22 6:46 ` Adam Wolfe Gordon
2012-02-21 5:59 ` Austin Clements
2012-02-21 16:49 ` Adam Wolfe Gordon
2012-02-22 16:57 ` 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=20120217170457.GE5991@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).