Seth Daniel

You have correctly identified the problem with lazy loading this plugin *while also* expecting it to work correctly on start. I think the correct answer is: don't lazy load this...

It's not a dependency. If you don't have `mason-lspconfig` this plugin continues to work. However I do see the point about loading `mason-lspconfig` too soon being a problem. I can...

*that could disrupt the flow of certain Neovim configurations* Can you describe your particular situation in more detail? I don't know for certain but it may help.

The output for checkhealth looks pretty bad when the current buffer is attached to `gopls` since it ends up printing a very large 'help' page (that `gopls` spits out) as...

I don't have a particularly good solution for fixing this unless it's possible to simply make the 'end' either 0 or 1 (whichever is the lowest possible number).

Looks like this 500 value is also used [here](https://github.com/bscan/PerlNavigator/blob/5b88333ea26119255964dde79d207df1ef548e49/server/src/diagnostics.ts#L138) and [here](https://github.com/bscan/PerlNavigator/blob/5b88333ea26119255964dde79d207df1ef548e49/server/src/diagnostics.ts#L289). I don't know if these particular instances affect recent neovim.

If you can retrieve the length of the line being jumped to that would be preferable. In looking at a few other language servers they seem to do something like...

One other option that may be simpler is to have 'end' be start line + 1 and character be 0. This assumes that there are at least start + 1...

Per conversation in #144 this issue was resolved upstream in https://github.com/neovim/neovim/issues/28281.