]> granicus.if.org Git - neomutt/commitdiff
docs: mention the choice of pinentry-program
authorDoron Behar <doron.behar@gmail.com>
Sat, 28 Jul 2018 12:40:01 +0000 (13:40 +0100)
committerRichard Russon <rich@flatcap.org>
Sat, 28 Jul 2018 12:40:01 +0000 (13:40 +0100)
init.h

diff --git a/init.h b/init.h
index fc5331a07140686b94b49f266172fd6b10230be9..d264f5255b9de68a80b94d0a29d61d2f69dfa936 100644 (file)
--- a/init.h
+++ b/init.h
@@ -2369,6 +2369,15 @@ struct ConfigDef MuttVars[] = {
   ** This is a format string, see the $$pgp_decode_command command for
   ** possible \fCprintf(3)\fP-like sequences.
   ** (PGP only)
+  ** .pp
+  ** Note: When decrypting messages using \fCgpg\fP, a pinentry program needs to
+  ** be invoked unless the password is cached within \fCgpg-agent\fP.
+  ** Currently, the \fCpinentry-tty\fP program (usually distributed with
+  ** \fCgpg\fP) isn't suitable for being invoked by NeoMutt.  You are encouraged
+  ** to use a different pinentry-program when running NeoMutt in order to avoid
+  ** problems.
+  ** .pp
+  ** See also: https://github.com/neomutt/neomutt/issues/1014
   */
   { "pgp_decryption_okay",      DT_REGEX,  R_NONE, &PgpDecryptionOkay, 0 },
   /*