undotree VS vimspector

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.

There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.

I struggle a bit to put what i want into words but i still try my best.So i got some plugins likehttps://github.com/sindrets/diffview.nvimhttps://github.com/harrisoncramer/gitlab.nvimhttps://github.com/puremourning/vimspectorand so on (but those are the one which i need that "feature" the most).

The actual title is "Vimspector - A multi-language debugging plugin for Vim".

It is a UI around DAP: https://github.com/puremourning/vimspector#what-vimspector-i...

vimspector

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

You could try vimspector. It's main target is vim and not neovim.

https://github.com/puremourning/vimspector/

I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).

[0] https://github.com/ycm-core/YouCompleteMe

[1] https://github.com/puremourning/vimspector

[2] https://github.com/dense-analysis/ale

For debugging normally I'd throw a breakpoint() and then have it launch pdb in a terminal from within nvim, but vimspector also exists if you'd rather.