nvim-dap-go VS DAPInstall.nvim

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).

nvim-dap-go

For Go, we can use nvim-dap-go which only require the following lines:

For golang debugging you may use nvim-dap (the dap client) and nvim-dap-go (a nvim-dap configuration for golang)

I creator of [plugin for golang development](https:/github.com/olexsmir/gopher.nvim), what do you think to add the dap config for go? To my mind, it'll be like dap-go.

There's a PR to merge the change into the author's repository here: https://github.com/leoluz/nvim-dap-go

Hey, nvim-dap-go creator here.

To run your debugger, first, you need to install the needed debugger. To do this, run: :DIInstall followed by a tab. Go here to view the documentation on it.

In addition to the sibling comment, I used https://github.com/Pocco81/DAPInstall.nvim It provides some default configuration for a lot of debuggers.

For a nice out of the box experience with nvim-dap you'd probably want to use DAPInstall.nvim.

I posted about DAPInstall.nvim a long time ago. If you don't know what it is, basically this plugin is like the :LspInstall but for debuggers. You can install with a simple command (:DIInstall ) and there is a default config for each one of the debuggers, which you can overwrite.

You could use, for instance, the python one as an example to write an installer for any of the debuggers supported by Nvim-dap.