vim-matchup VS undotree

Then you have all the vimscript plugins, most of which work in neovim too--my favorite of these is vim-matchup

It seems like https://github.com/andymass/vim-matchup is a superior version of both of them, at least that's how it's advertized.

Have you tried vim-matchup?

andymass/vim-matchup - nicer %

Thank you for you answer! This is the best option I've found by far. But some aditional steps need to be done to enable this behavior. It is documented here vim-matchup

vim-matchup does both of this things

If you don't wanna deal with matchparen, you could also consider using vim-matchup, which has better performance than matchparen and can match way more tokens and keywords.

vim-matchup improves these motions.and has a lot of nice features.

vim-matchup is written in lua, isn't it? https://github.com/andymass/vim-matchup/tree/master/lua

https://github.com/andymass/vim-matchup Plus come custom highlight groups

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.