Re: [PATCH] fix indent_string handling with format=flowed
> * Johannes Stezenbach [07-10-12 23:14:21 +0200] wrote:
>> I think it would be useful to have a config option to disable
>> RFC 3676 handling of received messages altogether and make mutt
>> behave like a plain old non-f=f aware MUA.
> Mutt with $text_flowed unset ignores the spaces and leaves them in. When
> such an option was added and the standard text/plain handler be used
> instead of the f=f handler, you'd still have the same problem: the message
> interpreted as f=f would lead to some flowable paragraphs.
> That would mean mutt doesn't need an option to disable f=f handling but to
> "downgrade" f=f to format=fixed by removing all trailing spaces?
> Mutt internally doesn't clearly distinct between rendering for display and
> rendering for a reply but it just passes around flags. So a downgrade still
> would have to use the f=f handler with omitting the spaces. Lines 136/137
> would have to be changed to something like:
> if (pos + line < len &&
> !option(OPTTEXTFLOWED) && option(DOWNGRADEFLOWED))
> state_putc (' ', s);
What I have in mind is an option to tell mutt to not use
the f=f handler to interpret the message. I guess I could
edit the Content-Type and delete "; format=flowed", but I would
prefer an option which I could toggle with a hotkey, so that
I could usually leave f=f handling enabled but quickly disable
it in those cases where it gets in the way.
The implementation of that option would just prevent the
"handler = rfc3676_handler;" assignment in mutt_body_handler(),
thus treating the mail as plaintext.
I think a good name for that option would be "handle_flowed"
or "decode_flowed", default "yes".
>> That would be especially
>> useful in those cases where people send patches inlined in
>> f=f messages, where the patch is actually OK but displayed wrapped.
> It may not be as clear as it should in the manual, but setting $text_flowed
> is a really bad idea when sending out formatted content like patches. And
> it's up to the user to take special care then using $text_flowed.
I'm concerned with interpreting bad content sent by others (e.g.
Thunderbird users are notorious for falling into this trap).
Me, I never ever set $text_flowed. (Maybe I'll do in the future
on occasion now that I know how it works ;-)