unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Matthew Lear <matt@bubblegen.co.uk>
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: Sat, 23 Jul 2016 09:40:17 -0400	[thread overview]
Message-ID: <878tws4gn2.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <3d06c4bede0643230bea93cb5d58ca6d.squirrel@webmail.plus.net>

Matthew Lear <matt@bubblegen.co.uk> writes:

> 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 guess lack of feedback as to whether the patch actually fixes the problem.

> 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?

Perhaps you or dme could send an updated version of the patch to the
list, as git-format-patch output (i.e. with a commit message and other
metadata).

d

      reply	other threads:[~2016-07-23 13:40 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
2016-07-23 13:40                                   ` David Bremner [this message]

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=878tws4gn2.fsf@maritornes.cs.unb.ca \
    --to=david@tethera.net \
    --cc=dme@dme.org \
    --cc=markwalters1009@gmail.com \
    --cc=matt@bubblegen.co.uk \
    --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).