yeah, those are called lenses (or code lenses) as you guessed

how can i disable them? they just started popping up after an update

that's a good question. The answer will most likely be some nvim configuration setting (of which I know nothing about) as I don't believe clojure-lsp has any flags for disabling that (which I guess makes sense as that's a client feature).

I know nothing about nvim, but have you checked out this https://neovim.io/doc/user/lsp.html#lsp-codelens?

This should be configurable in the client indeed, it's code lens capability that should be set to true or false, not sure how to do it in nvim

does that suggestion help? https://github.com/AstroNvim/AstroNvim/issues/1814#issuecomment-1521881344

https://github.com/AstroNvim/AstroNvim/blob/main/lua/astronvim/options.lua#L56 is where the distribution seems to set it, so using the suggestion should fix it.

doesn't work 😕

Where have you put the change in? It could be that astronvim loads before the setting is set. I’m no expert in Astro as well 😅

how can i check for vim.g options in : ?

i want to see the value for vim.g.codelens_enabled

:let g:codelens_enabled
g:codelens_enabled     v:false

it's false, but still seeing the "references" virtual text

Right, hence im thinking the option could set after astro nvim has loaded. did you put the option in your init.lua?

you can also use :lua= vim.g.codelens_enabled to get a better view of lua things

thanks, still:

:lua= vim.g.codelens_enabled
false

which means i set it right and still not working

Yeah probably an Astro related thing then. There’s something with the order in which it’s picking up. Definitely nothing to do with lsp.

yes, astronvim bug https://github.com/AstroNvim/AstroNvim/issues/1814#issuecomment-1525725110

thanks for assistance!

they just uploaded a fix 7m ago 🙂 fixed