changeset: 6701:b62483975c94
user:      Kevin McCarthy <ke...@8t8.us>
date:      Wed Jun 29 12:25:34 2016 -0700
link:      http://dev.mutt.org/hg/mutt/rev/b62483975c94

Clarify oppenc option documention. (closes #3846)

Rephrase the option description to try and make it clearer what the
option does, and how to enable/disable it within a message.

diffs (32 lines):

diff -r 2baed7154180 -r b62483975c94 init.h
--- a/init.h    Tue Jun 28 16:06:22 2016 -0700
+++ b/init.h    Wed Jun 29 12:25:34 2016 -0700
@@ -506,19 +506,19 @@
   ** .pp
   ** Setting this variable will cause Mutt to automatically enable and
   ** disable encryption, based on whether all message recipient keys
-  ** can be located by mutt.
-  ** .pp
-  ** When this option is enabled, mutt will determine the encryption
-  ** setting each time the TO, CC, and BCC lists are edited.  If
-  ** $$edit_headers is set, mutt will also do so each time the message
+  ** can be located by Mutt.
+  ** .pp
+  ** When this option is enabled, Mutt will enable/disable encryption
+  ** each time the TO, CC, and BCC lists are edited.  If
+  ** $$edit_headers is set, Mutt will also do so each time the message
   ** is edited.
   ** .pp
-  ** While this is set, encryption settings can't be manually changed.
-  ** The pgp or smime menus provide an option to disable the option for
-  ** a particular message.
+  ** While this is set, encryption can't be manually enabled/disabled.
+  ** The pgp or smime menus provide a selection to temporarily disable
+  ** this option for the current message.
   ** .pp
   ** If $$crypt_autoencrypt or $$crypt_replyencrypt enable encryption for
-  ** a message, this option will be disabled for the message.  It can
+  ** a message, this option will be disabled for that message.  It can
   ** be manually re-enabled in the pgp or smime menus.
   ** (Crypto only)
    */

Reply via email to