go plugin fails healthcheck with: "attempt to index global '_GO_NVIM_CFG' (a nil value)"

[luan]

go plugin fails healthcheck with: "attempt to index global '_GO_NVIM_CFG' (a nil value)"

[robdimsdale]

Also in case it's relevant, I'm using go1.18.1 darwin/amd64

[luan]

I can't seem to repro this, and the failure is coming from the plugin. Are you able to reproduce it consistently? It might be worth opening an issue on ray-x/go.nvim instead

[robdimsdale]

So, I can resolve this issue by adding require'go'.setup() to the before.lua in the ~/.config/nvim/lua/user/ directory. However, that seems like something that would be part of this config, rather than user-provided.

Without that change, it is 100% reproducible on my machine - uninstalling neovim (and the python plugins etc) and this config, and reinstalling it, and it consistently fails.

In my comment above I liked to a closed issue on ray-x/go.nvim which suggests that to fix the problem I'm having:

Make sure require'go'.setup() is called before require'go.lsp'.config()

I don't understand enough of this flow to understand why I need to add this config explicitly whereas it just works for you.

That seems like the sort of thing that would belong in this config. I don't know where I would make that change - I tried

[luan]

You had said that adding that to before.lua didn't solve the problem, that's why I thought it'd be something else. I'll add it in the right place.

[luan]

Can you try after this change?

[robdimsdale]

That seems to fix it.

Before when I was reproducing it, I think I was accidentally adding the line require'go'.setup() to the user.defaults/before.lua not user/before.lua. But my understanding was that these two files would be processed the same way. Maybe I got that wrong.

[robdimsdale]

Thank you for adding this. I still don't understand why you weren't running into this. I assume you had updated all of your plugins?

[luan]

No idea why it wasn't happening for me, but yeah, updated and on multiple computers. user.defaults is just a template that gets copied to the git ignored user folder. I admit that's a confusing thing since the folder is always there. I might spend some brain cycles trying to smooth that over later.

…

On May 11, 2022, 20:02 -0700, Rob Dimsdale-Zucker ***@***.***>, wrote: Thank you for adding this. I still don't understand why you weren't running into this. I assume you had updated all of your plugins? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[robdimsdale]

Alright - I think we're good to close this now. Thank you for your help!