In this thread automatic backups were discussed. Note version control by manually saving versions is indeed a different task. I took a look into drafts and it works different than what I have in my mind. I would be interested to hear how and for what purpose you use a version history like in drafts.
In drafts you can restore once saved versions but with two main differences to what I imagined as version control: 1. After restoring a version it remains with its old content as preset for a future restoration. I rather thought that by continuing working on that version the content of that version changes automatically by adaption to what you have added to the note. And 2. after restoring a version you loose the content of the note before restoration.
When we talk about version control we seam to mean two different tasks:
-
Actually there is just one note that keeps different versions as a backup for replacing the current note (like in draft)
-
You have real versions and each version changes with the process of working with that version
Would be interested to hear what would be more preferable 