undotree VS zest.nvim

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.

Zest: similar to Aniseed, but much less expansive. It's a good option if you want a bit less diy if you want to deal with macros

zest provides some macros for configuring Neovim and is usable with Hotpot or Aniseed.

Thanks for mentioning zest! I'm certain that it will remain primarily a macro library. I've disabled the tiny compiler it ships with by default to prevent any confusion. As such, it should be compatible with hotpot out of the box.

I would greatly appreciate it if linked to zest.nvim in your readme.

Another plugin that gave me realization is zest.nvim, which uses the Fennel language to simplify configuration by a lot. Fennel's lispyness, REPL, and macros is gonna be a huge boost in Neovim productivity.

Also, this is a shameless plug, but I'm working on a macro library that aims to streamline the configuration process of neovim with fennel. It is a heavy WIP, but I think at this point it conveys the general idea reasonably well. See tsbohc/zest.nvim for more details.