Eike Rathke wrote: > On Sunday, 2015-07-05 13:40:43 -0700, Brendan Cully wrote: > > > Older GPGMEs are missing CMS (S/MIME) support. Don't force the poor > > users to hit enter every time they start mutt. > > What is "older" exactly? And could we assume that anyone using a recent > mutt would not be using such "older" GPGME?
I don't know. Brendan actually mentioned he was getting hit with the prompt for the CMS engine. So, he, at least, is using a recent mutt with an older GPGME version. I added the checks in df55f14f4585 in place of the GPG_AGENT_INFO env var check. I'm actually pretty ambivalent about them, and am just as happy to drop the checks completely. > ... removing also the OpenPGP check failure confirmation doesn't look > very appealing to me, the error message will just fly by and may get > unnoticed while GPGME is really expected to support OpenPGP. I think it will be pretty obvious if the GPGME backend isn't working, and this will at least leave a message on stderr indicating something isn't quite right. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA http://www.8t8.us/configs/gpg-key-transition-statement.txt
signature.asc
Description: PGP signature
