unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Matthew Lear" <matt@bubblegen.co.uk>
To: "David Bremner" <david@tethera.net>
Cc: "Matthew Lear" <matt@bubblegen.co.uk>,
	notmuch@notmuchmail.org, "David Edmondson" <dme@dme.org>,
	"Mark Walters" <markwalters1009@gmail.com>
Subject: Re: (emacs) Parsing problems replying to encrypted html
Date: Fri, 22 Jul 2016 17:47:22 +0100	[thread overview]
Message-ID: <3d06c4bede0643230bea93cb5d58ca6d.squirrel@webmail.plus.net> (raw)
In-Reply-To: <87lh4wj4kq.fsf@zancas.localnet>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

Hi David,

> OK, with that setting I can duplicate the problem replying to encrypted
> HTML mail.
>
> It's also true that notmuch-reply doesn't include the content in the
> html version of the multipart/alternative. Unlike notmuch show, it
> doesn't have the ability to send parts later, so I guess that's a
> problem there.
>
> The following patch seems to fix it for me. What I haven't worked out is
> if it will break other things. Perhaps David E or Mark (in copy) can
> comment on whether this is a sensible change, given that we now give the
> user control of showing the part on the emacs side.
>
> diff --git a/notmuch-reply.c b/notmuch-reply.c
> index 3c6d685..cd88d79 100644
> --- a/notmuch-reply.c
> +++ b/notmuch-reply.c
> @@ -690,7 +690,7 @@ notmuch_reply_format_sprinter(void *ctx,
>
>      /* Start the original */
>      sp->map_key (sp, "original");
> -    format_part_sprinter (ctx, sp, node, TRUE, TRUE, FALSE);
> +    format_part_sprinter (ctx, sp, node, TRUE, TRUE, TRUE);
>
>      /* End */
>      sp->end (sp);

I could have sworn that I replied to this thread months ago but can't find
a record it in the archives... I think I also missed David E's reply to
yours mentioning the patch from id:1459708823-1852-1-git-send-email-dme at
dme.org, so I'm following up...

With David E's patch, the decryption problem I reported is resolved.
However, I notice that this change hasn't yet been committed / pushed. Is
there a particular reason for this?

I'm currently maintaining a version of this patch compatible with the
current master which makes this change to notmuch-mua.el
notmuch-mua-reply() by adding (notmuch-show-process-crypto process-crypto)
before doing the show. I've attached that patch here.

I just wondered if we were going to see this pushed to master any time soon?

Cheers,
--  Matt

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fix-encrypted-html.patch --]
[-- Type: text/x-patch; name="fix-encrypted-html.patch", Size: 942 bytes --]

diff --git a/emacs/notmuch-mua.el b/emacs/notmuch-mua.el
index 0445975..0dcdb06 100644
--- a/emacs/notmuch-mua.el
+++ b/emacs/notmuch-mua.el
@@ -250,7 +250,11 @@ mutiple parts get a header."
 		       ;; Don't omit long parts.
 		       (notmuch-show-max-text-part-size 0)
 		       ;; Insert headers for parts as appropriate for replying.
-		       (notmuch-show-insert-header-p-function notmuch-mua-reply-insert-header-p-function)
+                       (notmuch-show-insert-header-p-function notmuch-mua-reply-insert-header-p-function)
+                       ;; Ensure that any encrypted parts are
+                       ;; decrypted during the generation of the reply
+                       ;; text.
+                       (notmuch-show-process-crypto process-crypto)
 		       ;; Don't indent multipart sub-parts.
 		       (notmuch-show-indent-multipart nil))
 		    (notmuch-show-insert-body original (plist-get original :body) 0)

  parent reply	other threads:[~2016-07-22 16:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 13:09 (emacs) Parsing problems replying to encrypted html Matthew Lear
2016-03-01 13:38 ` David Edmondson
2016-03-01 13:59   ` Matthew Lear
2016-03-07  9:24     ` Matthew Lear
2016-03-07 12:20       ` David Bremner
2016-03-07 21:01         ` Matthew Lear
2016-03-08 11:22           ` David Bremner
2016-03-08 11:44             ` Matthew Lear
2016-03-08 12:08               ` David Bremner
2016-03-08 12:28                 ` Matthew Lear
2016-03-08 12:26             ` Tomi Ollila
2016-03-08 12:39               ` Tomi Ollila
2016-03-08 14:06                 ` Matthew Lear
2016-03-10 12:09               ` David Bremner
2016-03-10 12:23                 ` David Edmondson
2016-03-12 13:33               ` David Bremner
2016-03-12 14:37                 ` David Edmondson
2016-03-13 16:09                   ` Jani Nikula
2016-03-14  8:32                     ` David Edmondson
2016-03-31 19:20                   ` Matthew Lear
2016-04-01 11:34                     ` David Bremner
2016-04-01 11:54                       ` Matthew Lear
2016-04-01 13:28                         ` David Bremner
2016-04-01 13:58                           ` Matthew Lear
2016-04-01 18:29                             ` Matthew Lear
2016-04-01 23:24                               ` David Bremner
2016-04-03 18:42                                 ` David Edmondson
2016-07-22 16:47                                 ` Matthew Lear [this message]
2016-07-23 13:40                                   ` David Bremner

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=3d06c4bede0643230bea93cb5d58ca6d.squirrel@webmail.plus.net \
    --to=matt@bubblegen.co.uk \
    --cc=david@tethera.net \
    --cc=dme@dme.org \
    --cc=markwalters1009@gmail.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).