unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Edmondson <dme@dme.org>
To: David Bremner <david@tethera.net>,
	Tomi Ollila <tomi.ollila@iki.fi>,
	Matthew Lear <matt@bubblegen.co.uk>
Cc: notmuch@notmuchmail.org
Subject: Re: (emacs) Parsing problems replying to encrypted html
Date: Sat, 12 Mar 2016 14:37:44 +0000	[thread overview]
Message-ID: <m2shzvrccn.fsf@dme.org> (raw)
In-Reply-To: <87wpp76ctq.fsf@zancas.localnet>

On Sat, Mar 12 2016, David Bremner wrote:
> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 --reply-to=sender thread:0000000000004a6f
>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 id:56DDE706.6060702@bubblegen.co.uk
>> 2016-03-08 (Tue) 14:16:01: show --format=sexp --include-html --part=3 id:56DDE706.6060702@bubblegen.co.uk
>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=3 id:56DDE706.6060702@bubblegen.co.uk
>>
>
> I think the problem is in the following let form, which uses
> notmuch-show-process-crypto. That isn't set in search mode. I'm unclear
> on what the right solution is here; we could check
> notmuch-crypto-process-mime, but I'm not sure how this would interact
> with the handling of prefix arguments (for temporary toggling).

Is "reply" from search mode a common pattern of use? Currently it seems
generally un-useful (the thread has to contain just a single message -
not just a single matching message).

> (defun notmuch-mua-reply (query-string &optional sender reply-all)
>   (let ((args '("reply" "--format=sexp" "--format-version=1"))
> 	(process-crypto notmuch-show-process-crypto)
> 	reply
> 	original)

  reply	other threads:[~2016-03-12 14:37 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 [this message]
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

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=m2shzvrccn.fsf@dme.org \
    --to=dme@dme.org \
    --cc=david@tethera.net \
    --cc=matt@bubblegen.co.uk \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).