Re: Support for encoding format=flowed (RFC 2646)

[Niklas Morberg <niklas.morberg@axis.com>]

Matt Armstrong <matt@lickey.com> writes:

> I do use filladapt.

Me too. [Turning filladapt off and use-hard-newlines on.
Testing...]. Turning off filladapt (`M-x filladapt-mode')
did not seem to help, though. I still see the same problem.

> What I was seeing was that stuff like the quoted text
> above or the automatically inserted ~/.signature would
> have a hard newline at the end of each line (longlines.el
> showed them to me). Then each hard newline in the message
> buffer ended up as two newlines in the sent message.

Exact same behaviour here (except possibly for the .sig
stuff which I haven't tested). Also, long text strings (such
as URLs) break with a `=' character at the end. The message
contains this information after being received:

 Content-Type: text/plain; charset=iso-8859-1; format=flowed
 Content-Transfer-Encoding: quoted-printable
 
 
 http://tiny-tools.sourceforge.net/emacs-elisp-body.html#longlines.el_aut=
 oma=3D=20
 tically_wrap_long_lines

Which in my article buffer renders like this (hoping that
this formatting stuff will still show after sending):

 http://tiny-tools.sourceforge.net/emacs-elisp-body.html#longlines.el_automa=
 tically_wrap_long_lines

Oh well, I'll just not use hard newlines for the time being.

Niklas