Re: format=flowed revisited...

In message <[email protected]>, [email protected] 
writes:
>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?

It could screw up paragraphs with lots of QP-characters, that
when they're QP encoded have a long line with a '=$', a short line, a
long line with a '=$', a short line and so on.

Also, can't you do this already by setting horizontal scrollbar side
to none and the width of the message display to 80 or whatever you
want it to be? I just tried a really long line and exmh broke the line
up for me.

//Christer

-- 
| Hagåkersgatan 18C | Phone: Home +46 31 43 52 03   CTH: +46 31 772 5431  |
| S-431 41 Mölndal  |        Cell: +46 707 53 57 57                       |
| Sweden            | Mail:  [email protected]                             |
"An NT server can be run by an idiot, and usually is." -- Tom Holub, a.h.b-o-i


_______________________________________________
Exmh-workers mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-workers