Sometimes while in an inbox you can type a c and it will say "continue interrupted composition" but this seems rather spiratic.
In this case I open a new ssh session with the new IP, kill the previous session (which also kills alpine), and then when I resume alpine I can use "C I" to resume interrupted mail composition
When the user chooses to cancel a message within Alpine (^C, then C to confirm), Alpine saves the cancelled message to ${HOME}/dead.letter. This behaviour can optionally be disabled in your settings.
When the Alpine process is terminated gracefully (i.e., by a catchable signal: a regular "kill" from another window, ssh connection dies, host gets gracefully shutdown/rebooted, etc), it writes any message in progress to ${HOME}/.pine-interrupted-mail before gracefully exiting. As far as I know, this cannot be disabled in settings. When Alpine starts back up again, it checks for a ${HOME}/.pine-interrupted-mail file, and, if it finds one, it offers you to resume your interrupted composition.
As far as I know, Alpine has no mechanism to periodically "auto-save" a message in progress. So if the Alpine process is terminated *ungracefully* (e.g., non-catchable signal such as "kill -9", host loses power, etc), then your message will be lost. The only workaround that comes to mind is that you could use an external editor that does offer auto-save. vim, for example, frequently auto-saves your work in progress, so that if it dies unceremoniously, you can recover your work from pretty close to the time that it died. In a case like this, Alpine could not automatically help you find and resume the interrupted message; it would be up to you to know where/how the editor places its auto-saves and to recover the one you're looking for.
-Jason _______________________________________________ Alpine-info mailing list [email protected] http://mailman23.u.washington.edu/mailman/listinfo/alpine-info
