On Wed, 14 Sep 2022 09:37:14 +0200 (CEST) local10 <loca...@tutanota.com> wrote:
> I actually have it disabled on purpose. The reason is I don't always > want changes to be autosaved because sometimes the changes make the > document worse. I wonder if there's some change tracking option in LO > that would allow to see how the document developed over time. If you check the checkbox found at: Edit → Track Changes → Record it will do exactly that. Note that it records a *lot* of detail, and can bloat the file size if the edit history gets long. Personally, I store most of my documents in a Syncthing share and have the server-side Syncthing instance set to retain the last 'n' versions of the file. Each autosave is a new 'version', so there's a balance between autosave frequency and number of retained versions. Eg autosave every 30 minutes, retain last 10 versions, that allows 5 hours of continuous working before the state of the file before I sat down to start the day gets pushed off the stack. If you want to go all in on "how the document developed over time" and are comfortable with git, I gather it's possible to set up git hooks that will unpack the compressed odt file on the fly and commit the version-able, diff-able contents to a git repo, and vice versa. This would enable true version control, including branching, tagged release versions, and so forth. I've never tried this, and can't vouch for how smoothly it works in practice. Cheers! -Chris
