Closed unhammer closed 3 years ago
It doesn't retain changes across run
, because all the internal data gets replaced in that process.
As currently set up, the solution is to occasionally type save
(or v
).
Do you think it would make sense to autosave or prompt if there are unsaved changes before a run
?
Autosave. If all else fails, there's git history.
I would actually expect it to save on accept
, I don't see any point in a separate save
command
for some reason I had a notion in my head of minimizing file writes, but I'm definitely not doing that with the web interface...
I don't think most people type that fast =D
very annoying if you've carefully accepted/golded/skipped 30 things