Does nixvim have a lsp manager plugin?

[Mach1212]

I recently tried to migrate to nixvim but lspconfig's on_attach handlers kept annoying me.
The K key for hover was bound to multiple hover providers, etc.

Lazynvim and Astronvim both have solutions to this, but I really like configuring with nix not lua...

[MattSturgeon]

I'm not sure what you mean by a "LSP manager". But we do have the lsp.keymaps option, where you can define keymaps that'll only be registered on LspAttach.

[Mach1212]

I ran into an issue of on_attach pollution where lspconfig binds multiple, lets say hover handlers, to a key. Then these all run at the same time.
Like when I press K once...

I get two notifications, if not three when typescript-tools, cssls, and tailwindcss are all attached.

I researched that astronvim and lazynvim have a global on_attach handler that prevents this pollution and bind one handler that collects the responses from all the attached lsps, but I don't want to write my own or configure lsp integration with them. I want a nixvim solution.

Let me know if I'm misunderstanding something.

[MattSturgeon]

Are you talking about per-server on_attach defined via vim.lsp.config() vs the global LspAttach autocmd?

Nixvim has a lsp.onAttach option that allows defining lines of lua that are run in the autocmd, similar to what some distros do with their global on_attach.

[Mach1212]

I'm not sure so let me zoom out a little.

I am trying to setup a webdev nixvim config with lspsaga.
How would I setup the lsp.servers and lsp.onAttach so whenever K is pressed it runs :Lspsaga hover_doc?

When I added global nixvim keymaps for K then lspsaga hover would work, but I would get the above notify message multiplied by however many servers "failed" to find hover information.

But I don't think thats how the notification/handler should work?

[Mach1212]

I found a workaround. I can just mute the messages.