ctrlsf.vim VS undotree

Here is an example of a plugin spec for ctrlsf.vim.

This has been clutch for me https://github.com/dyng/ctrlsf.vim

You can try this plugin https://github.com/dyng/ctrlsf.vim . It provides something similar to what you explained, but you need to scope it manually if you want it only for current buffer.

I use ctrlsf.vim - how does your plugin compare to that one? Would it be a potential replacement now or in the future?

There is dyng/ctrlsf.vim, specificaly the edit-mode

There's also ctrlsf

Cool. Looks interesting! I use less known (I think) plugin called CtrlSF, which gives the same type of functionality. In my experience, CtrlSF has a very good user interface and feels intuitive to use.

ctrlsf

ctrlsf.vim - Project Wide Find + Replace (req)

If you are not a fan of the quickfix list have a look at ctrlsf.vim. It's more like Sublime text's search and replace.

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.