klonk VS undotree

While surfing the web I came across this blog post: Resolving the Great Undo-Redo Quandary.

Resolving the Great Undo-Redo Quandary\ (31 comments)

My goofy lil' homemade editor does it this way: If you go back in the past and change it, the future becomes the past. This might sound confusing, but effectively it means that the undo stack contains the actual history of "what happened". This means you can hop to any past or future state linearly with undo & redo alone. I just find this easier than navigating tree GUIs and things that aren't worth the trouble to me. It can still lead to a bit of mental gymnastics in extreme cases.

https://github.com/zaboople/klonk

Note that in theory this can cause an exponential growth of the undo/redo stacks because it makes an upside-down copy of the future when you change the past; but in practice it's never been an issue.

I was thinking of adding a feature to navigate back to "last change-the-past", which wouldn't be hard.

It at least makes more sense than most science fiction time-travel plots...

What's helped me much more lately is undotree for vim [1]. It basically logs every single time a file is saved. Its much more useful because commits have to be made by humans and they may not do it often (and usually there is an incentive for "clean or working commits"). There have been many times where I went back to copy something from the undotree.

[1]: https://github.com/mbbill/undotree

Hi, I love Vim, and use it for big projects too, with many files. Often I switch between many files, make changes, undo, and get lost in them, trying to find a file that I edited and undoed a few minutes ago. I think, maybe exists some plugin, that will visualize my history of changes, like UndoTree, but across multiple buffers? And/or list of my teleportations between buffers? I can imagine this, also like a tree...

The plug-in could be found here

undotree

undotree: tree like visualization of undo history

Install undo tree and your life turns into a choose your own adventure story.

> I really hate autosave. I like using saving like a checkpoint where i have the ultimate undo button by ditching the unsaved changes.

Although I don't use autosave, I don't think it matters that much with vim because you can always use undotree[0]

0: https://github.com/mbbill/undotree

I finally got around to clear up the vague notions I had about the `g+` and `g-` commands which I knew helped me jump to across branches but was never exactly sure how. With the help of undotree module, it is now crystal clear what the difference was between `u` and `g-` and between `` and `g+` are.

Here the link: https://github.com/mbbill/undotree

Vim has a plugins for that too. ;)

I use https://github.com/mbbill/undotree but if that's not to your choice there are many others.