William Casarin writes:
> I've started collecting[1] a bunch of notmuch+GitHub hacks from some of
> the discussions @ id:87d16jtsdj@kyleam.com
> [..]
>
> [1] https://github.com/jb55/notmuch-github
> [2]
> https://github.com/jb55/notmuch-github/commit/fb2d80cf9ee9a5967c78ae6ccda866ee98cdd547
On Tue, Jun 19 2018, Daniel Kahn Gillmor wrote:
> Many of the manpages didn't treat literal text as literal text. I've
> tried to normalize some of the restructured text to make it a bit more
> regular.
>
> several of the synopsis lines are still untouched by this cleanup, but
> i'm not sure what
Daniel Kahn Gillmor writes:
> Many of the manpages didn't treat literal text as literal text. I've
> tried to normalize some of the restructured text to make it a bit more
> regular.
>
pushed.
d
___
notmuch mailing list
notmuch@notmuchmail.org
https:
Daniel Kahn Gillmor writes:
> @@ -270,7 +274,7 @@ _notmuch_message_crypto_potential_payload
> (_notmuch_message_crypto_t *msg_crypto
> if (parent && GMIME_IS_MULTIPART_ENCRYPTED (parent) && childnum ==
> GMIME_MULTIPART_ENCRYPTED_VERSION) {
> const char *enc_type = g_mime_object_get_
Daniel Kahn Gillmor writes:
> +
> +# TODO:
> +# * check S/MIME as well as PGP/MIME
Decrypting S/MIME would be good first step. Or is the feature there
(with gmime 3.0?) but tests missing? because T355-smime says there is no
S/MIME decryption.
> +# * process headers protected by signature
> +