++ 07/01/15 14:57 -0800 - Kevin J. McCarthy:
I'm wondering if that is sufficient for people interested in the patch, or whether a quadoption for postpone_encrypt would be more useful. For a quadoption, I would keep the behaviour the same: the quadoption would only be consulted if the message encryption flag was set.
Thanks for the patch, I will apply it one of these days. Seems to be a usefull addition for me. I don't need the quadoption solution, but that may be different for other people. However, a quadoption would somewhat make it more consistent with the other options.
Would it be useful to be able to encrypt, even if the message encryption flag is not set? If so, I could use some opinions, because defining the interface for that starts to get complicated.
To me, that is of no particular use.
Against what version is the patch you have provided? -- Rejo ZengerE r...@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J r...@zenger.nl
OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF
pgpqj5KBWf9GJ.pgp
Description: PGP signature