On 02Sep2022 15:27, Cameron Simpson <c...@cskk.id.au> wrote:
On 01Sep2022 20:18, Kevin J. McCarthy <ke...@8t8.us> wrote:
I'm not sure if it helps at this point, but I can report that I've
taken your template above and passed it to 'mutt -H' and the resulting
sent file has format=flowed in its content-type header. :-/
Can you try directly doing this too, outside of your tmux-editing
framework?
Yes. I should have done that already. [...]
I'll be back after I've done some cleaner experiments.
So, a bare "mutt -H" here acts like yours, honouring the Content-Type
header. This points the finger directly at my script, where I discovered
a problem.
First up, it is necessary to hand apply a Content-Type header to the
template file (as implied by the $text_flowed documentation).
Second, my script was:
- grabbing the template filename from the command line as $filename
- making the copy to be used by the tmux session's "mutt -H" as $tmpf
- patching the copy with a Content-Type header
- assigning filename=$tmpf after the copy was complete, for use in the
following code
During debugging I'd stuck that in a subshell, a habit when I turn on
"set -x" in a script, thus:
blah blah ...
( set -x
code beging traced
...
...
)
So the filename= assignment was lost, and the subsequent run-in-tmux
code was using the unpatched no-Content-Type file.
Fixed and deployed.
This message should be format=flowed.
Cheers,
Cameron Simpson <c...@cskk.id.au>
