[mew-int 2667] Re: format=flowed

[Harald Hanche-Olsen]

+ Kazu Yamamoto (山本和彦) <kazu at example.com>:

>>> I have implemented the encoding of format=flowed and fixed several
>>> bugs of the decoding.
>>
>> Thank you. From a little testing, it works fine except for one
>> thing: You should turn off longlines-mode before encoding the
>> buffer, as otherwise your code (mew-encode-flowed) will see soft
>> line breaks as hard ones, and the paragraphs are broken into lines.
>>
>> In order to avoid autoloading longlines.el in vain I suggest code like
>>
>> (if (and (boundp 'longlines-mode) longlines-mode) (longlines-mode-off))
>>
>> inserted in the right place.
> 
> Thank you. I have merged this code.

In some cases, turning off longlines-mode in mew-smtp-encode-message
is too late. If my buffer looks like this:


To: hanche at example.com
Subject: Test
From: Harald Hanche-Olsen <hanche at example.com>
References: <a-very-long-reference-that-is-bound-to-move-into-the-next-line at example.com>
  <another-reference at example.com>
X-Mailer: Mew version 6.1.53 on Emacs 23.0.60 / Mule 6.0 (HANACHIRUSATO)
----
Test message.


and I turn on longlines-mode and hit C-cC-m, then the result is the malformed


To: hanche at example.com
Subject: Test
From: Harald Hanche-Olsen <hanche at example.com>
<a-very-long-reference-that-is-bound-to-move-into-the-next-line at example.com>
  <another-reference at example.com>
X-Mailer: Mew version 6.1.53 on Emacs 23.0.60 / Mule 6.0 ----
Test message.
----


And before you ask, yes, this has happened to me in practice, and as a
result I sent a malformed message to a mailing list.

So longlines-mode needs to be turned off before mew gets to look at
any headers, I think.

- Harald