From: Jani Nikula <jani@nikula.org>
To: notmuch@notmuchmail.org
Cc: jani@nikula.org, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: [PATCH 3/7] cli/reply: unify reply format functions
Date: Sun, 19 Jun 2016 00:31:29 +0300 [thread overview]
Message-ID: <bef407ca64fd6340c4d48e5111adcca68a8d7c11.1466284726.git.jani@nikula.org> (raw)
In-Reply-To: <cover.1466284726.git.jani@nikula.org>
In-Reply-To: <cover.1466284726.git.jani@nikula.org>
Prepare for further future unification by making the code similar. The
only functional change is that errors in mime_node_open() also break
execution in default reply format.
---
notmuch-reply.c | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/notmuch-reply.c b/notmuch-reply.c
index 5adbab624ad7..4b97ffa4f096 100644
--- a/notmuch-reply.c
+++ b/notmuch-reply.c
@@ -604,20 +604,20 @@ notmuch_reply_format_default(void *ctx,
unused (sprinter_t *sp))
{
GMimeMessage *reply;
- mime_node_t *root;
+ mime_node_t *node;
+
+ if (mime_node_open (ctx, message, ¶ms->crypto, &node))
+ return 1;
reply = create_reply_message (ctx, config, message, reply_all);
if (!reply)
return 1;
show_reply_headers (reply);
+ format_part_reply (node);
g_object_unref (G_OBJECT (reply));
-
- if (mime_node_open (ctx, message, ¶ms->crypto, &root) == NOTMUCH_STATUS_SUCCESS) {
- format_part_reply (root);
- talloc_free (root);
- }
+ talloc_free (node);
return 0;
}
@@ -633,7 +633,7 @@ notmuch_reply_format_sprinter(void *ctx,
GMimeMessage *reply;
mime_node_t *node;
- if (mime_node_open (ctx, message, ¶ms->crypto, &node) != NOTMUCH_STATUS_SUCCESS)
+ if (mime_node_open (ctx, message, ¶ms->crypto, &node))
return 1;
reply = create_reply_message (ctx, config, message, reply_all);
@@ -645,7 +645,6 @@ notmuch_reply_format_sprinter(void *ctx,
/* The headers of the reply message we've created */
sp->map_key (sp, "reply-headers");
format_headers_sprinter (sp, reply, TRUE);
- g_object_unref (G_OBJECT (reply));
/* Start the original */
sp->map_key (sp, "original");
@@ -654,6 +653,9 @@ notmuch_reply_format_sprinter(void *ctx,
/* End */
sp->end (sp);
+ g_object_unref (G_OBJECT (reply));
+ talloc_free (node);
+
return 0;
}
--
2.1.4
next prev parent reply other threads:[~2016-06-18 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 21:31 [PATCH 0/7] cli/reply: refactoring Jani Nikula
2016-06-18 21:31 ` [PATCH 1/7] cli/reply: push notmuch reply format abstraction lower in the stack Jani Nikula
2016-06-18 21:31 ` [PATCH 2/7] cli/reply: reuse show_reply_headers() in headers-only format Jani Nikula
2016-06-18 21:31 ` Jani Nikula [this message]
2016-06-18 21:31 ` [PATCH 4/7] cli/reply: reorganize create_reply_message() Jani Nikula
2016-06-18 21:31 ` [PATCH 5/7] cli/reply: make references header creation easier to follow Jani Nikula
2016-06-18 21:31 ` [PATCH 6/7] cli/reply: reuse create_reply_message() also for headers-only format Jani Nikula
2016-06-18 21:31 ` [PATCH 7/7] cli/reply: reduce the reply format abstractions Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 0/6] cli/reply: refactoring part 2 Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 1/6] cli/reply: use dedicated functions for reply to mapping Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 2/6] cli/reply: check for NULL list first in scan_address_list() Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 3/6] cli/reply: return internet address list from get header funcs Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 4/6] cli/reply: pass internet address list to munge detect Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 5/6] cli/reply: pass gmime message to munge detection Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 6/6] cli/reply: only pass gmime message to add recipients to reply message Jani Nikula
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=bef407ca64fd6340c4d48e5111adcca68a8d7c11.1466284726.git.jani@nikula.org \
--to=jani@nikula.org \
--cc=dkg@fifthhorseman.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).