On 31Aug2022 15:37, Kevin J. McCarthy <ke...@8t8.us> wrote: >On Thu, Sep 01, 2022 at 08:11:50AM +1000, Cameron Simpson wrote: >>The essential problem is that I run a separate mutt instance using "mutt >>-H" on a copy of my message template. The manual does say that >>$text_flowed has no effect then, but I seem to have no other way to >>apply the needed header - adding it by hand during composition is >>ineffective. >> >>I _might_ do better adding it to the copy before starting the separate >>mutt; I'll see if that works. > >I think this may work best for you, if the my_hdr approach doesn't work.
It seems to have no effect; the Content-Type eg from my reply just now to you is still not format=flowed. I did discover that an illegal Content-Type causes the "mutt -H" to abort. >Content-Type and other MIME headers aren't included in the "edit >headers" generated headers, and they aren't parsed afterwards either. Ok. I can see why that might be done, since in effect I'm editing a text attachment in some ways. I'm a little surprised one can't modify Content-Type though. That seems like something which would make sense in the "edit headers"; it feels like an "in the attachment" header. What if I wanted to send markdown? (I know there's a whole thread about this somewhere, to which I didn't pay enough attention at the time; I'll find it). >If you haven't played with it before, you might also look into >background editing and the contrib/bgedit-screen-tmux.sh script. See ><http://www.mutt.org/doc/manual/#bgedit>. I will; the background editing feature postdated my tmux games. Cheers, Cameron Simpson <c...@cskk.id.au>
