alt Hacker NewsThe point about linting still stands, though. I recently had to grep for a note I was really sure was there, but didn't show in the roam-find- autocomplete. Turns out, at some point I must've accidentally put a stray character that made properties section stop parsing, dropping the note from the system. Another case is when I occasionally add what I intend to be roam note as a new org file, and then forget to press the shortcut I have to give the file an ID.
(EDIT: Similarly, over the years I had a few cases of some TODOs I forgot about because I accidentally made a whole subtree stop parsing with a stray character. Rare as it is, I'm beginning to wonder if I shouldn't switch to modal editing a la vim, as those mistakes tend to happen when moving through the outline with "speed keys".)
In general, Org works well for me, but damn if the fragility of plaintext doesn't bite me every now and then.
Replies
You can use a combination of auto-save-visited-mode (this will save to the actual file, rather than a backup) and gitwatch to auto commit all changes. It should prevent most forms data loss or desynchronization.
> The point about linting still stands, though.
Do you run org-lint on the save hook? I wonder if that'd be too distracting, or if it can be done silently unless some errors detected.
> fragility of plaintext
For that, I have .dir-locals.el file in the root of my notes folder with a single line: ((org-mode . ((eval git-auto-commit-mode 1))))
Even if I accidentally make a change, there's always trackable history