order of sending mail and saving to fcc

[Cameron Simpson]

On 11Jun2019 20:21, Nicolas Rachinsky <mutt-users-1 at ml.turing-complete.org> wrote:
>* Derek Martin <invalid at pizzashack.org> [2019-06-11 12:47 -0500]:
>> Not only that, but I neglected the fact that if the send fails, the
>> file your editor produced in order for it to be passed to Mutt will
>> still be on disk, so you do IN FACT still have a copy of the message.
>
>I did just (using my old mutt) set sendmail to killall -9 mutt. The
>temporay file that stayed on my disk did contain my text. But there
>was no other information (recipients, subject, attachments).
>
>So if the tmpdir survives, not everything is lost. But the mail as
>such is lost.

Just to this.

I compose with edit_headers=yes, so recipients and subject are part of 
the temporary file.

Also, I attach using the Attach: pseudo header, so the attachment 
filename is also part of the temp file. Provided I haven't exited the 
compose mode (when the Attach: headers turn into actual mutt 
attachments) I don't lose that state either. (I've also got 
fcc_attach=yes, might be handy too.)

And to ease using the Attach: header I have this vi macro:

  map ^A 1G}-:.r!exec </dev/tty 2>/dev/tty; readline -B 'Attach: '^MIAttach: ^[

Those are literal ctrl-A, ctrl-M, ctrl-[ (escape) in the macro. This 
means that I just type ctrl-A to commence an attachment and I get a file 
competion capable prompt to fill out the filename.

Oh yes, readline itself is a little shell script to invoke bash to use 
its GNU readline mode:

  https://bitbucket.org/cameron_simpson/css/src/tip/bin/readline

because it is so useful.

Hoping this improves your compose environment,
Cameron Simpson <cs at cskk.id.au>