saving draft messages, getting rid of pgpmime line

[Tamas Papp]

Hi,

I just upgraded to latest mu4e master (to partake in the new query
parser goodness, which is indeed working out great). At the same time I
updated to Ubuntu 17.10, so I am not sure which change is causing these
two minor issues:

1. C-c C-d used to save the messages as a draft, now it calls
message-dont-send, which just buries the buffer. Can I still save the
message as a draft? Did that get a new shortcut, or is there a function
name I should rebind C-c C-d to?

2. starting a message with mu4e-compose-new, it starts with a line

secure method=pgpmime mode=sign

between <>'s. My mu4e-compose-crypto-reply-policy is nil, but I guess it
should not affect things anyway. Can I turn this off somehow?

Best,

Tamas

[Yuri D'Elia]

On Fri, Oct 27 2017, Tamas Papp wrote:
> 2. starting a message with mu4e-compose-new, it starts with a line
>
> secure method=pgpmime mode=sign
>
> between <>'s. My mu4e-compose-crypto-reply-policy is nil, but I guess it
> should not affect things anyway. Can I turn this off somehow?

Set the new mu4e-compose-crypto-reply-plain-policy to nil.

I actually welcome this change.
I turn it on/off depending on the context.

[Dirk-Jan C. Binnema]

Having it set to 'sign as the default is probably a bit too aggressive
though, so I've change the default to nil.

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

[Tamas Papp]

On Sat, Oct 28 2017, Dirk-Jan C. Binnema wrote:

> On Saturday Oct 28 2017, Yuri D'Elia wrote:
>
>> On Fri, Oct 27 2017, Tamas Papp wrote:
>>> 2. starting a message with mu4e-compose-new, it starts with a line
>>>
>>> secure method=pgpmime mode=sign
>>>
>>> between <>'s. My mu4e-compose-crypto-reply-policy is nil, but I guess it
>>> should not affect things anyway. Can I turn this off somehow?
>>
>> Set the new mu4e-compose-crypto-reply-plain-policy to nil.
>>
>> I actually welcome this change.
>> I turn it on/off depending on the context.
>
> Having it set to 'sign as the default is probably a bit too aggressive
> though, so I've change the default to nil.

Thanks, it is back to its previous behavior now.

Can someone please help me with the other question (C-c C-d used to save

the messages as a draft, now it calls message-dont-send, which just

buries the buffer)?

best,

Tamas

[Dirk-Jan C. Binnema]

On Saturday Oct 28 2017, Tamas Papp wrote:

> Can someone please help me with the other question (C-c C-d used to save
> the messages as a draft, now it calls message-dont-send, which just
> buries the buffer)?

mu4e inherits the binding from message-mode/gnus, and afaik as I know
`C-c C-d` has always been bound to `message-dont-send' which, at least
here, saves the buffer to draft and then buries the buffer.

When I subsequently jump to my draft folder, the message is there.