Re: mutt: 5 new changesets
* Kyle Wheeler wrote:
> How hard would it be for mutt to re-wrap format=flowed messages
> before sending, in order to guarantee that the lines are less than
> the format=flowed limit (72/79 characters).
That wouldn't be too hard.
> More generally... RFC 2646 says:
(2646 is obsoleted by 3676)
> A generating agent SHOULD:
> 1. Ensure all lines (fixed and flowed) are 79 characters or
> fewer in length, counting the trailing space but not
> counting the CRLF, unless a word by itself exceeds 79
> 2. Trim spaces before user-inserted hard line breaks.
> 3. Space-stuff lines which start with a space, "From ", or
> Granted, the mutt-format=flowed relationship is a somewhat rocky one,
> relying on the person's editor to do most of the heavy lifting. I
> don't think mutt can be held responsible for #2, and probably not for
> #3, but I think mutt *can* do #1.
As documented in the manual, mutt does #3 after the initial editing of a
message, except space-stuffing before '>' because it can't separate
quotes from '>' in text. For #2, ACK. For #1, mutt already does that
when preparing a reply, though you can break that rule by changing the
wrapping accordingly in the editor. I think the user is responsible for
sending something sane out, I'm not convinced mutt should change a
message without the user having a chance to intercept.
The same counts for length limits in other areas. For example, when you
have lines longer than 990 characters, mutt chooses quoted-printable
encoding to work around the limit -- but you can see that and change it
in the compose menu. It doesn't do that "behind your back" right before