From ddea2de317b2ac08736b8fdf74b7075bfd312ac9 Mon Sep 17 00:00:00 2001 From: Vincent Lefevre Date: Mon, 29 Apr 2019 12:49:22 +0200 Subject: [PATCH] Corrected minor errors in text related to $forward_attachments Co-authored-by: Richard Russon --- doc/manual.xml.head | 2 +- send.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/manual.xml.head b/doc/manual.xml.head index 646883d72..dcde4af97 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -3182,7 +3182,7 @@ color sidebar_divider color8 default # Dark grey $forward_decode=yes) is to use standard inline forwarding. In that mode all text-decodable parts are included in the new message body. Other attachments from - the original email can also attached to the new message, based on the + the original email can also be attached to the new message, based on the quadoption $forward_attachments. diff --git a/send.c b/send.c index 9b8e21b1a..86bde4a7a 100644 --- a/send.c +++ b/send.c @@ -584,9 +584,9 @@ static int inline_forward_attachments(struct Mailbox *m, struct Email *cur, This is the prompt for $forward_attachments. When inline forwarding ($mime_forward answered "no"), this prompts whether to add non-decodable attachments from the original email. - Text/plain parts and the like will be already be included in the + Text/plain parts and the like will already be included in the message contents, but other attachment, such as PDF files, will also - be added as attachments to the new mail, is this is answered yes. + be added as attachments to the new mail, if this is answered yes. */ _("Forward attachments?")); if (*forwardq != MUTT_YES) -- 2.40.0