From 4d3019da7c234990b15e7fa66f80678f027c7554 Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Sat, 25 Jul 2020 11:32:15 +0300 Subject: [PATCH] mu4e.texi: remove obsolete crypto footnote. Fixes #1761. --- mu4e/mu4e.texi | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index c1a7f5fc..52eaa60b 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -1504,11 +1504,9 @@ profile) that does not load images. The same applies to Javascript. @node MSGV Crypto @section Crypto -The @t{mu4e} message view supports@footnote{Crypto-support in @t{mu4e} -requires @t{mu} to have been build with crypto-support; see the -@ref{FAQ}} decryption of encrypted messages, as well as verification of -signatures. For signing/encrypting messages your outgoing messages, see -@ref{Signing and encrypting}. +The @t{mu4e} message view supports decryption of encrypted messages, +as well as verification of signatures. For signing/encrypting messages +your outgoing messages, see @ref{Signing and encrypting}. For all of this to work, @command{gpg-agent} must be running, and it must set the environment variable @t{GPG_AGENT_INFO}. You can check from