Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

put markdown files on /tmp prevent notes recovery #389

Open
SamirSaidani opened this issue Feb 22, 2018 · 2 comments
Open

put markdown files on /tmp prevent notes recovery #389

SamirSaidani opened this issue Feb 22, 2018 · 2 comments

Comments

@SamirSaidani
Copy link

SamirSaidani commented Feb 22, 2018

When your computer crashes, all files on /tmp (usually a mem filesystem) are automatically cleaned after reboot.
If you were writing some notes at this moment, all your notes are lost.

One workaround is to allow another temporary directory, like $HOME/tmp and use vim recovery capabilities (vim -r) to recover your notes.

geeknote should allow at least to set another temporary directory, at best put all the markdown temporary files into .geeknote directory by default.

PS: I've just lost my half-page note :-/

@jeffkowalski
Copy link

jeffkowalski commented Feb 22, 2018 via email

@SamirSaidani SamirSaidani changed the title put markdown files on tmp prevent notes recovery put markdown files on /tmp prevent notes recovery Feb 23, 2018
@SamirSaidani
Copy link
Author

SamirSaidani commented Feb 23, 2018

It looks like vim and libreoffice programmers handle this edge case, so it makes sense that geeknote handle this case too, since note editing is a core feature of geeknote. System crashes is a part of the user experience, and as such resilient software design should be considered by the programmer.
TMPDIR looks good for me, or at least using $HOME/.geeknote/ to save temporary note files for a quick patch. Thanks for this nice software !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants