William Boman

Hello, thanks for your feedback! > Nothing happens. No warning, No message -- I would expect some error message to occur. Ah, yeah this should probably show a warning. >...

I was also thinking of mimicing the nvim-treesitter behavior for this, but the code is not very well suited for capturing the stdout/stderr currently - the UI window "owns" all...

Yep this is on the roadmap. What I want to solve first is to only update servers that actually needs updating. I think just naively re-installing all installed servers doesn't...

Also, I'd like to solve #154 before doing this as well. Currently if the updating of a server fails, the server will effectively become uninstalled. This'll be _really_ annoying if...

A little sneak peak https://user-images.githubusercontent.com/6705160/141648667-94218eb8-95ad-46c9-884f-3e65b393d92c.mov

Update: The complexity in implementing this (in a robust and undiscriminating1 manner) is that there's virtually no information stored about installed servers - other than the fact that it's "installed"...

See https://github.com/williamboman/nvim-lsp-installer/pull/395 for an initial implementation of checking for outdated servers. It's currently only tied to the UI (no command yet, will add later, will have to think about rate...

I found this: https://github.com/clangd/clangd/issues/722#issuecomment-795295250. This doesn't seem like anything that can be fixed here - maybe there could be a check for which glibc version is installed to make sure...

> The function `.get_installed_servers()` will still be supported in the future? That function will remain!

> Does that include `server:on_ready(function() ... end)` as in: The `on_ready()` function is deprecated as well! Note that you can now remove that snippet of code in your example that...