vim-clap VS vimspector

I'm thrilled to share that the latest vim-clap has now integrated the tree-sitter highlighting into Vim and NeoVim. It's a PoC implementation and not extensively tested though, bugs are expected. Some early feedback is highly appreciated, and read more in this post!

It has been two years since I last posted about the update of vim-clap. A lot of features have been added to vim-clap since then, check out the CHANGELOG if you are interested. Today I want to share with you a feature that I want to support in vim-clap for quite a long time: the search syntax of fzf, which is powerful yet pretty handy in my opinion. Feel free to try #738 and leave some feedback.

Free free to test the PR #738 and leave some feedback.

I'll also take the occasion to recommend clap.vim, which is the picker I use. It's super cool, fast, and uses a rust backend for more intensive searches.

- https://github.com/nvim-telescope/telescope.nvim or https://github.com/liuchengxu/vim-clap for file navigation (I'm still deciding which one I will continue to use)

vim-clap supports filer so I can search for files in different directories outside my project.

(For me) New vimscript fuzzy finder I was unaware about: https://github.com/liuchengxu/vim-clap (the search field is a vim buffer which I loved)

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.