vim-go VS vimspector

I found a github issue that seems related, but following the steps to start dlv on my own does not work either. https://github.com/fatih/vim-go/issues/3543

There are a handful of really good go plugins that take care of this for you, such as https://github.com/ray-x/go.nvim or https://github.com/fatih/vim-go

With vim-go and snippets, neovim has almost the same functionality as GoLand

So does anyone know how to actually install it? The "instructions" (which I presume had to be dictated by their straight-jacketed author) from GitHub are, utterly useless, requiring the user to already have vim-go installed before beginning vim-go installation. You'll need vim-go to install vim-go, you see, because with a working vim-go installation can the user execute the special command to install vim-go's dependencies (because that's how software works ya know). And, if you have any trouble installing vim-go, it says, not to worry - further instructions have been provided along with your existing vim-go installation - just execute `:help go-install` (requires existing vim-go installation, of course) and from there, it's turtles all the way down! So as long as you have vim-go installed, installing vim-go is a breeze! Am I having an anheurysm right now? What the hell is this?

git clone https://github.com/fatih/vim-go.git ~/.local/share/nvim/site/pack/plugins/start/vim-go

with this wonderful plugin: https://github.com/fatih/vim-go

Hi, usually Vim works as expected: scroll mouse event move a buffer content for a few lines. But sometimes something broke and every scroll event move a whole screen, like I pressed PageUp or PageDown. I thought that this is a defect with some plugin - because I can reproduce it only with vim-go and mouse=a - without other plugins and configs. I tried multiple terminals, and even boot Ubuntu live USB - still reproducible with my private company codebase, so I cannot share the code. This is my ticket for that plugin - the author said that this is might be something with my system configuration. Please help.

At first Ihad struggled with some common "IDE" tasks. But then I discovered vim-go and realized that it could do pretty much everything that I need and even more.

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.