On 2019-06-04, Jack M <j...@forallx.net> wrote: > On Tue, June 4, 2019 10:46 am, Grant Edwards wrote: >> On 2019-06-04, Jack M <j...@forallx.net> wrote: >> >> >>> The reason (or *a* reason) is that the old way led to the following >>> situation: Fcc first, then try to send, something weird happens, but >>> the user has no idea whether the mail was actually sent or not >> >> How could the user not know? > > Very easily. > >> If the send fails, mutt prints an error message and stays on the message >> compose screen. > > The part starting with "and" is not always true, though. I've been bitten > several times by mutt flashing an error message so quickly that I can't > read it, and then immediately showing an empty inbox with a completely > different error message about a lost connection to the IMAP server.
Then that's a bug, and it needs to be fixed. If you try to send a message and it fails, there's no way you should leave the message compose screen. Changing the order of the send/fcc operations to try to hide problems like that seems odd. -- Grant
