On 02Sep2022 08:15, Cameron Simpson <[email protected]> wrote:
>Trying that with this reply.
Well, that tossed my Content-Type header and sent with:
Content-Type: text/plain; charset=us-ascii
I'm trying again here, for thoroughness. The source file starts like
this:
Content-Type: text/plain; charset=utf-8; format=flowed
From: Cameron Simpson <[email protected]>
To: [email protected]
Cc:
Bcc: [email protected]
Subject: Re: trouble with my_hdr and $format_flowed
Reply-To:
In-Reply-To: <[email protected]>
and the Content-Type is not presented in this current editor.
Interestingly, the process tree looks like this:
cameron 94359 1116 4299624 1220 \_ /bin/sh ~/bin/rmafter
~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 mutt -e set
editor=vim-flowed -e unset signature -e set sidebar_visible=no -H
~/var/mutt/mutt-fleet2-501-83365-16591433053586932493
cameron 94361 94359 4345688 11628 \_ mutt -e set editor=vim-flowed -e
unset signature -e set sidebar_visible=no -H
~/var/mutt/mutt-fleet2-501-83365-16591433053586932493
cameron 94383 94361 4403212 12656 \_ vim -c silent 1,/^$/s/ *$// -c
set filetype=mail -c set formatoptions=walqj
~/var/mutt/mutt-fleet2-501-94361-4463746866273406678
and the file ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493
passwd to "mutt -H" is already gone. Does mutt remove it?
Ah, mutt might have move it to ~/var/mutt/compose/muttedit.94328, which
exists with the header above.
Let's look at the Content-Type on this message...
Cheers,
Cameron Simpson <[email protected]>
