On Tue, Nov 20, 2012 at 12:52:58PM -0600, David Champion wrote: > A welcome addition to this thread would be information on how to > compose in "qpff" using mutt.
http://mutt-ng.berlios.de/manual/format-flowed.html is the one I've seen before. Also noticed this, though I don't know if it's correct: http://vim.wikia.com/wiki/Correct_format-flowed_email_function I do agree that format=flowed is the "right" thing to do *if* you want to send mail that can be read at any line width. Many common mail clients and webmail providers generate mail this way. Personally, I think that mutt's handling of it, while reasonable, could still be improved, both in terms of delay and in terms of quoting. However, correct me if I'm wrong, but I think vim (with the 'w' formatoption) is the only console-based editor with support for generating flowed text properly, and even in that case, from what I understand, it doesn't work 100% perfectly. I think rfc2646 is one case where mutt's lack of integration between MUA and editor becomes a bit problematic - the MUA ultimately is what needs to ensure that the message being sent complies with the rfc (at the time of sending), but mutt delegates formatting to the editor, and I'm pretty sure you could manage to generate a non-compliant or improperly formatted message in vim, even with fo+=w. Multiple quote levels seems to be problematic too, from what I remember (that is, mutt doesn't mangle it so that all text that mutt *displays* as quoted is generated as quoted text when dumped into the user's $editor). As far as quoting flowed text, I don't love mutt's current handling of it -- I still prefer the behavior of patch-1.5.5.1.gj.stuff_all_quoted.3 (space-stuffing all quoted lines vs. just the last one, which is obviously the more conservative way to go). If anyone's updated this patch for current mutt, let me know - Gary's email seems to have changed. w
