Re: (emacs) Parsing problems replying to encrypted html

2016-07-23 Thread David Bremner
Matthew Lear 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

Re: (emacs) Parsing problems replying to encrypted html

2016-07-22 Thread Matthew Lear
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

Re: (emacs) Parsing problems replying to encrypted html

2016-04-03 Thread David Edmondson
On Sat, Apr 02 2016, David Bremner wrote: > Matthew Lear writes: > Hmm. I can't duplicate the problem replying from show mode with the test message you provided. Is the appropriate key in your gpg keyring? >>> >>> Yes it is. I get the gpg gui

Re: (emacs) Parsing problems replying to encrypted html

2016-04-01 Thread David Bremner
Matthew Lear writes: >>> Hmm. I can't duplicate the problem replying from show mode with the test >>> message you provided. Is the appropriate key in your gpg keyring? >> >> Yes it is. I get the gpg gui prompt when opening the encrypted email and >> can decrypt it prior to

Re: (emacs) Parsing problems replying to encrypted html

2016-04-01 Thread Matthew Lear
>> Hmm. I can't duplicate the problem replying from show mode with the test >> message you provided. Is the appropriate key in your gpg keyring? > > Yes it is. I get the gpg gui prompt when opening the encrypted email and > can decrypt it prior to show. As I suspected earlier in the thread, I >

Re: (emacs) Parsing problems replying to encrypted html

2016-04-01 Thread Matthew Lear
> Matthew Lear writes: > >> Thanks David. I've just pulled and rebuilt and can see a difference. >> When >> replying from show view, I see no quoted text from the original message, >> but when I reply from search view I see the inline PGP ciphertext quoted >> in the reply. I

Re: (emacs) Parsing problems replying to encrypted html

2016-04-01 Thread David Bremner
Matthew Lear writes: > Thanks David. I've just pulled and rebuilt and can see a difference. When > replying from show view, I see no quoted text from the original message, > but when I reply from search view I see the inline PGP ciphertext quoted > in the reply. I can

Re: (emacs) Parsing problems replying to encrypted html

2016-04-01 Thread Matthew Lear
> Matthew Lear writes: > >> On Sat, Mar 12 2016 at 2:37:44 pm GMT, David Edmondson >> wrote: >>> On Sat, Mar 12 2016, David Bremner wrote: Tomi Ollila writes: > 2016-03-08 (Tue) 14:16:01: reply --format=sexp

Re: (emacs) Parsing problems replying to encrypted html

2016-04-01 Thread David Bremner
Matthew Lear writes: > On Sat, Mar 12 2016 at 2:37:44 pm GMT, David Edmondson wrote: >> On Sat, Mar 12 2016, David Bremner wrote: >>> Tomi Ollila writes: >>> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1

Re: (emacs) Parsing problems replying to encrypted html

2016-03-31 Thread Matthew Lear
On Sat, Mar 12 2016 at 2:37:44 pm GMT, David Edmondson wrote: > On Sat, Mar 12 2016, David Bremner wrote: >> Tomi Ollila writes: >> >>> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 >>> --reply-to=sender thread:4a6f >>>

Re: (emacs) Parsing problems replying to encrypted html

2016-03-14 Thread David Edmondson
On Sun, Mar 13 2016, Jani Nikula wrote: > On Sat, 12 Mar 2016, David Edmondson wrote: >> 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). > > I

Re: (emacs) Parsing problems replying to encrypted html

2016-03-13 Thread Jani Nikula
On Sat, 12 Mar 2016, David Edmondson wrote: > 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). I wish we could make it useful again. It was one of

Re: (emacs) Parsing problems replying to encrypted html

2016-03-12 Thread David Edmondson
On Sat, Mar 12 2016, David Bremner wrote: > Tomi Ollila writes: > >> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 >> --reply-to=sender thread:4a6f >> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 >> id:56dde706.6060...@bubblegen.co.uk

Re: (emacs) Parsing problems replying to encrypted html

2016-03-12 Thread David Bremner
Tomi Ollila writes: > 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 > --reply-to=sender thread:4a6f > 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 > id:56dde706.6060...@bubblegen.co.uk > 2016-03-08 (Tue) 14:16:01: show --format=sexp

Re: (emacs) Parsing problems replying to encrypted html

2016-03-10 Thread David Edmondson
On Thu, Mar 10 2016, David Bremner wrote: > Tomi Ollila writes: > >> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 >> --reply-to=sender thread:4a6f >> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 >> id:56dde706.6060...@bubblegen.co.uk

Re: (emacs) Parsing problems replying to encrypted html

2016-03-10 Thread David Bremner
Tomi Ollila writes: > 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 > --reply-to=sender thread:4a6f > 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 > id:56dde706.6060...@bubblegen.co.uk > 2016-03-08 (Tue) 14:16:01: show --format=sexp

Re: (emacs) Parsing problems replying to encrypted html

2016-03-08 Thread Matthew Lear
> On Tue, Mar 08 2016, Tomi Ollila wrote: > >> [ text/plain ] >> On Tue, Mar 08 2016, David Bremner wrote: >> >>> [ text/plain ] >>> Matthew Lear writes: >>> >>> >>> Thanks for the test case. I can duplicate a (the?) bug as >>> follows. Replying to that message from

Re: (emacs) Parsing problems replying to encrypted html

2016-03-08 Thread Tomi Ollila
On Tue, Mar 08 2016, Tomi Ollila wrote: > [ text/plain ] > On Tue, Mar 08 2016, David Bremner wrote: > >> [ text/plain ] >> Matthew Lear writes: >> >> >> Thanks for the test case. I can duplicate a (the?) bug as >> follows. Replying to that message from notmuch-show mode

Re: (emacs) Parsing problems replying to encrypted html

2016-03-08 Thread Matthew Lear
>> Hmm. In emacs, if I try to reply to the message from notmuch-search, I >> get >> no error but there is no quoted text from the original message in the >> reply body and all I see is the 'on , wrote:' citation. >> Replying from notmuch-show gives me the error I mentioned previously. > > I

Re: (emacs) Parsing problems replying to encrypted html

2016-03-08 Thread Tomi Ollila
On Tue, Mar 08 2016, David Bremner wrote: > [ text/plain ] > Matthew Lear writes: > >>> >>> Please encrypt a message to the attached gpg key (from the notmuch test >>> suite), and send it to the list as an attachement if you can replicate >>> the bug. >> >> Done. Attached

Re: (emacs) Parsing problems replying to encrypted html

2016-03-08 Thread David Bremner
Matthew Lear writes: > > Hmm. In emacs, if I try to reply to the message from notmuch-search, I get > no error but there is no quoted text from the original message in the > reply body and all I see is the 'on , wrote:' citation. > Replying from notmuch-show gives me the

Re: (emacs) Parsing problems replying to encrypted html

2016-03-08 Thread Matthew Lear
> Thanks for the test case. I can duplicate a (the?) bug as > follows. Replying to that message from notmuch-show mode works, but > replying from notmuch-search mode yields > >> !!! Bodypart insert error: Wrong type argument: number-or-marker-p, nil >> !!! >> [ application/pgp-encrypted ] >>

Re: (emacs) Parsing problems replying to encrypted html

2016-03-08 Thread David Bremner
Matthew Lear writes: >> >> Please encrypt a message to the attached gpg key (from the notmuch test >> suite), and send it to the list as an attachement if you can replicate >> the bug. > > Done. Attached here. > > [ >

Re: (emacs) Parsing problems replying to encrypted html

2016-03-07 Thread Matthew Lear
On Mon, Mar 07 2016 at 12:20:37 pm GMT, David Bremner wrote: > Matthew Lear writes: >> >> This is easy to reproduce on linux with thunderbird (I'm using v38.5.0). >> Edit -> Account Settings -> Composition & Addressing and check 'Compose >> messages in

Re: (emacs) Parsing problems replying to encrypted html

2016-03-07 Thread David Bremner
Matthew Lear writes: > > This is easy to reproduce on linux with thunderbird (I'm using v38.5.0). > Edit -> Account Settings -> Composition & Addressing and check 'Compose > messages in HTML format' and send yourself a pgp encrypted email using > PGP/MIME, open it in

Re: (emacs) Parsing problems replying to encrypted html

2016-03-07 Thread Matthew Lear
On 01/03/16 13:59, Matthew Lear wrote: >> There is probably a bug here. >> >> On Tue, Mar 01 2016, Matthew Lear wrote: >>> Notmuch shows this as: >>> >>> [ multipart/encrypted ] >>> [ Decryption successful ] >>> [ Good signature by: ] >>> [ application/pgp-encrypted ] >>> Version: 1 >>> [

Re: (emacs) Parsing problems replying to encrypted html

2016-03-01 Thread Matthew Lear
> There is probably a bug here. > > On Tue, Mar 01 2016, Matthew Lear wrote: >> Notmuch shows this as: >> >> [ multipart/encrypted ] >> [ Decryption successful ] >> [ Good signature by: ] >> [ application/pgp-encrypted ] >> Version: 1 >> [ multipart/mixed ] >> [ multipart/alternative ] >> [

Re: (emacs) Parsing problems replying to encrypted html

2016-03-01 Thread David Edmondson
There is probably a bug here. On Tue, Mar 01 2016, Matthew Lear wrote: > Notmuch shows this as: > > [ multipart/encrypted ] > [ Decryption successful ] > [ Good signature by: ] > [ application/pgp-encrypted ] > Version: 1 > [ multipart/mixed ] > [ multipart/alternative ] > [ text/plain

(emacs) Parsing problems replying to encrypted html

2016-03-01 Thread Matthew Lear
Hi, I've noticed a problem when replying to an encrypted email when I have html set as preferred over plain text. Looks like notmuch fails to parse the body and the original body text in notmuch-reply just looks like this: > [ text/html ] > !!! Bodypart insert error: End of file during parsing