Documentation updates for format=flowed

diff --git a/UPDATING b/UPDATING
index 944f8b65555a67d6b31b309fdbf08e21e4494521..c0daa39ecd2825040caad4ff6d342c4d8cb3b2a7 100644 (file)
--- a/UPDATING
+++ b/UPDATING
@@ -4,6 +4,7 @@ mutt. Please read this file carefully when upgrading your installation.
 The keys used are:
   !: modified feature, -: deleted feature, +: new feature
 
+  ! improved f=f support wraps lines at $wrap if $wrap is not 0
   + $wrap (>0 wraps at $wrap, <0 = $wrapmargin)
   + $assumed_charset, $attach_charset, $ignore_linear_white_space
   + $save_history, $history_file (save history across sessions)

diff --git a/doc/manual.xml.head b/doc/manual.xml.head
index 8e9624c601a71ef37a34d70fb7e1211b17fa6cd6..f5bad9e4bf0d5d1a26ee10fca4074d2aa122a92b 100644 (file)
--- a/doc/manual.xml.head
+++ b/doc/manual.xml.head
@@ -1243,10 +1243,27 @@ before calling the editor).
 After editing the initial message text and before entering
 the compose menu, mutt properly space-stuffes the message.
 <emphasis>Space-stuffing</emphasis> is required by RfC3676 defining
-<literal>format=flowed</literal> and means to prepend a space to all
-lines starting with a space and lines starting with the word
-<literal>From</literal> (followed by space). All leading spaces are to
-be removed by receiving clients to restore the original message.
+<literal>format=flowed</literal> and means to prepend a space to:
+</para>
+
+<itemizedlist>
+<listitem><para>all lines starting with a space</para></listitem>
+<listitem><para>lines starting with the word ``<literal>From</literal>''
+followed by space</para></listitem>
+<listitem><para>all lines starting with ``<literal>&gt;</literal>'' which
+is not intended to be a quote character</para></listitem>
+</itemizedlist>
+
+<para>
+All leading spaces are to be removed by receiving clients to restore
+the original message.
+</para>
+
+<para>
+<emphasis role="bold">Note</emphasis> that mutt only support space-stuffing
+for the first two types of lines but not for the third: It is impossible to
+safely detect whether a leading <literal>&gt;</literal> character starts a
+quote or not.
 </para>
 
 </sect3>