delve VS vim-go

At a recent job, we had slightly different containers for local dev; our backend containers (for a Go app) had Air [1] installed for live reloading, plus Delve [2] running inside the container for VS Code's debugger to connect to. We also had a frontend container for local dev, which didn't get deployed as a container, just as static files.

[1] https://github.com/cosmtrek/air

[2] https://github.com/go-delve/delve/

https://github.com/go-delve/delve/releases/tag/v1.21.2 Thanks Derek and the rest of the team for helping us to debug in a normal way!

My employer has a commercial solution for this but Delve does supports `rr` traces natively for this purpose, which gives a complete open-source solution (https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_replay.md).

delve and related IDE integrations

For time travel debugging in Go:

The Delve debugger for Go supports debugging rr traces: https://github.com/go-delve/delve/blob/master/Documentation/...

Undo (who I work for) maintain a fork that debugs our LiveRecorder recordings: https://docs.undo.io/GoDelve.html

Either rr (https://rr-project.org/) or our UDB debugger (https://undo.io/solutions/products/udb/) can do some time travel debugging of Go programs via GDB's built-in support for Go. I believe its weakness is in support for goroutines, since they don't map well onto its idea of how programs run.

So in my case I use https://github.com/leoluz/nvim-dap-go (which itself calls out to the CLI tool https://github.com/go-delve/delve).

Clone https://github.com/go-delve/delve.git

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.