I’m writing a manuscript in devonthink and came across a couple issues: short (inconsistent) undo/redo history and lack of file versioning.
My manuscript is broken up into separate files (markdown) for individual sections, grouped into a folders for intro, results, methods, etc. This helps me outline my paper and allows me to easily go back and forth between different parts. The problem is that if I’m writing in the preview pane of the main window (with the navigation and inspector), the undo history is lost every time I switch between different files. This has been a problem. I really don’t understand the behavior of the undo/redo commands and never know what will happen when I click undo. This does not happen when I command-open the text in a separate window, but I don’t want to have multiple windows open at once.
That brings me to a related issue: file versioning (sorry for having multiple topics). If I were to make a mistake that can’t be undone, I’d feel safer knowing that I can easily restore a previous version. What are the best ways to constantly keep a group of text files backed up? I use Time Machine but that’s only hourly. A smart rule is a good option, but I’m not sure how to properly set it up to monitor specific files. I have many large documents in my database that I want to exclude. But I don’t want to have to remember to tag every important file with something like #backup. Another option would be to store my manuscript folder in Dropbox and index it with devonthink. Dropbox has file versioning so this could be a good option.
Any suggestions? Am I missing something simple with the undo problem? What are your favorite ways to keep your important text backed up?