Feature request: re file persistence

[rmloveland]

trafficstars

I just had a super scary moment. I posted a review that I'd been working on for several hours and received this response from the Github API:

Submitting review... error: POST https://api.github.com/repos/cockroachdb/docs/pulls/3884/reviews: 502 Server Error []

I went into $TMPDIR and AFAICT re had deleted the file (unless I missed something obvious).

Luckily the Github user interface showed that my changes had gone through despite the error.

It would be good to have either (or maybe both) of:

1. Persistent re-edit* files in a directory (e.g., ~/.re), perhaps with filenames using UNIX timestamps so they can be more easily sorted (current implementation seems to add random number to the filename)
2. Really good API response error checking before exiting/cleaning up the temp file (maybe less necessary if we have the first point above, in which case we can rely on disk in general, possibly text editor autosave files if needed).

Open to other suggestions that would achieve the goal of not losing work in case of failure of some kind (machine power-off also comes to mind, since these files are in $TMPDIR).