format=flowed revisited...

[email protected] Mon, 20 Feb 2012 14:28:07 -0500
Newsgroups gmane.mail.exmh.devel
Message-ID <[email protected]>
I'm getting more and more mail that's obviously intended to be format=flowed,
but it isn't declared the in the Content-Type: header.  The end result is a
line that goes shooting off the right side of the window and an aggrivating
scrollbar to see the rest of the line/paragraph....

What do people think of changing the exmh code such that if the CTE is Q-P, and
we encounter a '=$' soft linebreak at the end of a line, we assume we're in
flowed mode even if it wasn't declared?

I still need to check what this does to my linux-kernel mail, where there's
often mix of inline C code that shouldn't be flowed, and text that should be.
Maybe needs to be handled on a paragraph-by-paragraph basis?

If people don't like that, what's a better heuristic?

_______________________________________________
Exmh-workers mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-workers
signature.asc (application/pgp-signature, 865 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iQIVAwUBT0KexwdmEQWDXROgAQKqJhAAuK7X2AsPyGq+eosBXsB3CfwniYbWlogJ
S6oJgH/X/j3AOkkAbTggBnZPNQCiCYMtxkrUzGLlaHS6Yqkk6cgaZo/jYW8Ys5ae
/W0Jo/7HT4hiQ9uXH4KyfJ1J9i+2weTaBmxqoB2hPnCo7lTBD4szB4RGQt3urQsE
3CeqCq6iIbfYNTNqY+KHr6mh+nuwqYp/TP8ACfojtTTu9yxNlR06gSRnj1HdYjf9
XcCBndHiB5IDoNnMSI7rrZAQCm4MeZXHHE/y4px4FKPAyTZCDWaXZSODSmilqJjz
w6eISgFg6Y0UDDtyNAljuQmBdbMZ8WFQr/1PdvTItHetGM6V5EigM7Xnb3psEGcX
lUy5WcaJNK3+tImti8pceXNRVYEcxsobuxY0VFHxNJEBBgXU4u1Zeiy74hXMrUhN
Rq+1LEUCma4rEYdMouzYodNs5vLesplEUtbIS9fWjrWI07sELA6I9dRZjmxxtPEL
PH/X+34V/2UksJRKyBjZ8lSuYY/eS0O0s4S48u3Vw7f0nT/OqJXuzWiujtkU8TZa
X3BRjKgh5N/fO5I/caq81jiePx5OZNU4FFt/aZZAI3lOuS+jKA4lxziJh8BPPbJI
krR0T/14K/S6XfqIiYT3kExWGJczxIE5KlrXKny94o99uOyHkjHigJwVvdLH6YkF
3mMXV2rL0Fg=
=60lb
-----END PGP SIGNATURE-----