From: Kevin McCarthy <kevin@8t8.us>
Date: Wed, 2 Mar 2016 23:08:54 +0000 (-0800)
Subject: Document that GPGME doesn't support creating inline PGP messages.
X-Git-Tag: neomutt-20160404~66
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6978d7328e4e0227b6413b85c5213709da6d574d;p=neomutt

Document that GPGME doesn't support creating inline PGP messages.
---

diff --git a/init.h b/init.h
index 065944f38..e00308dce 100644
--- a/init.h
+++ b/init.h
@@ -568,6 +568,9 @@ struct option_t MuttVars[] = {
   ** S/MIME and PGP will be used instead of the classic code.  Note that
   ** you need to set this option in .muttrc; it won't have any effect when
   ** used interactively.
+  ** .pp
+  ** Note that the GPGME backend does not support creating old-style inline
+  ** (traditional) PGP encrypted or signed messages (see $$pgp_autoinline).
   */
   { "crypt_use_pka", DT_BOOL, R_NONE, OPTCRYPTUSEPKA, 0 },
   /*
@@ -1732,7 +1735,8 @@ struct option_t MuttVars[] = {
   ** This option controls whether Mutt generates old-style inline
   ** (traditional) PGP encrypted or signed messages under certain
   ** circumstances.  This can be overridden by use of the pgp menu,
-  ** when inline is not required.
+  ** when inline is not required.  The GPGME backend does not support
+  ** this option.
   ** .pp
   ** Note that Mutt might automatically use PGP/MIME for messages
   ** which consist of more than a single MIME part.  Mutt can be