On 01Sep2022 08:50, Cameron Simpson <[email protected]> wrote:
>>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.
I don't think these things can do what I want.
The background editing feature seems to let you use an asynchronous
editor (a GUI or a tmux/screen session with suitable
wait-for-completion) and return immediately to mutt. Then have the
primary (the only) mutt do the post-edit sending when the editor
finishes. While that would let me, say, detach the tmux session and
resume it elsewhere, it wouldn't let me quit the primary mutt.
My approach runs an entirely separate mutt to edit-then-send the
message, and runs that as the "editor" in the primary mutt. I can finish
in the tmux session and send, and it feels exactly like invoking vim
directly from mutt. Or I can detach from the session, resume the primary
mutt, do whatever, and _quit_ the primary mutt. The tmux session lurks
around, ready for resumption later.
For example, as I type this my tmux listing contains:
14 mutt-01sep2022-09_09-Re__trouble_with_my_hdr_and_format_flowed: 1
windows (created Thu Sep 1 09:09:57 2022) (attached)
which is running "mutt -H -copy-of-the-original".
So I'm still left with the problem: how to invoke a "mutt -H" to send a
format=flowed message. Still striking out with that so far.
Cheers,
Cameron Simpson <[email protected]>
