1 This document lists bug known to exist in mutt-ng which are more less
4 RfC 3676 defining format=flowed
5 ===============================
7 This RfC specifies quote chars to be '>' and due to space-stuffing lines
8 there're no spaces withing the quote prefix of a line allowed.
9 Currently, the implementation does:
11 - Change all quote characters by force to '>'. This is plain wrong in
12 some cases where a character from $quote_regexp (even with the default
13 setting) may appear at the beginning of a line but actually doesn't
14 represent a quoted line. For example, someone may quote parts of
15 muttng configs with comments. However, _if_ this _is_ a quoted line
16 using e.g. '#' as $indent_string, we need to change the '#' prefix to
19 - Compress the complete quote, i.e. remove any spaces within the
20 complete quote prefix of a line. This, too, is just plain wrong. For
21 example, some people may have $indent_string set to '> ' and this gets
22 quoted several times to something like '>> >>'. However this
23 semanticly has a quote level of 3 as the second poster space-stuffed
24 that line. IMHO it's more common that people use spaces in
25 $indent_string (which the implementation removes right now) than
26 people space-stuffing lines which start '>' to ' >' when composing new
29 - Altough the standard enforces space-stuffing as a MUST, muttng
30 currently violates it. Space-stuffing is done once after initially
31 editing the message. The routine only handles '^From ' and '^ ' cases,
32 '^>' is ignored. (Once because an already space-stuffed line still has
33 a leading space so that it would get space-stuffed everytime the user