I've long had my mutt+vim setup to compose format=flowed email. There's
just one problem: it wasn't working. So I'm digging into why.
I've got:
set text_flowed=yes
in my setup. And if I pare down enough mutt settings, my reply goes out
with this header:
Content-Type: text/plain; charset=us-ascii; format=flowed
which is what I want (I've got send_charset="us-ascii:utf-8" so I
presume if I put some nonascii in then mutt would bump that to "utf-8").
But without paring things down, I do not get that header.
I have a pretty weird way of composing replies and new messages: I like
to be able to detach from the new message window. So I compose in a
separate tmux session. That is done via a special script I use for
$editor, which essentially goes:
- copy the message to a temp file
- start a tmux session running "mutt -H the-temp-file"
- quit
Because mutt silently drops back (and doesn't send) if the new message
didn't get modified, this gives me a tmux session where I compose the
message and send it, and then mutt silently discards my original, and
I'm back in the index or pager as before. This is seamless.
So what's wrong?
It appears that mutt does not put "format=flowed" in the "Content-Type"
header until message send time. The message I see in the editor before
compose does not have the header.
I think the fix would be to presupply the "Content-Type" header. I also
think such a fix might break the send_charset magic, unless mutt picks
up an existing Content-Type header, parses it, and fills in the
parameters if missing.
I've put a format=flowed into this message by hand, and I'll see if it
survives.
Thoughts?
Cameron Simpson <c...@cskk.id.au>
