vimspector VS vim-floaterm

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.

Using https://github.com/voldikss/vim-floaterm and remap the same shortcuts to (un)toggle the terminal would be interesting for you, also about compatibility, because if tomorrow you use nvim in the terminal you have the same key maps.

vim-floaterm has wrappers around some terminal filemanagers.

If you don't like distro's and want to use something of your own, make sure that you have a few plugins like telescope.nvim, lazy.nvim, toggleterm.nvim Or vim-floaterm, gitsigns.nvim, which-key.nvim, which will make your neovim journey smooth. Again these are just few, but I highly recommend it.

My personal favorite is ranger, a multi-panel console file manager that works nicely in a Neovim terminal. I also use floaterm to get floating terminal windows for ranger and lazygit, but that's optional. A Neovim tab with a terminal would work equally well.

For simple tasks like opening a dirty file in nvim I prefer vim-floaterm. It has a really nice integration with a bunch of TUI tools.

The two obvious candidates are vim-floaterm and toggleterm.nvim.

I’d suggest taking a look at vim-floaterm. While I don’t use this feature, it should have the ability to do what you’ve described

vimwiki + floatterm + vimwiki-sync