Skip to content

fix: update mason-lspconfig setup to not use deprecated handlers #1619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

moguls753
Copy link

Since the handlers setting is removed in mason-lspconfig v2.0, I think the following makes sense.

  • Remove deprecated handlers API and automatic_installation

  • Set automatic_enable = false since setup() is invoked explicitly

@guru245
Copy link
Contributor

guru245 commented Jun 27, 2025

Hi @moguls753
Would you care to see #1475 ? Does it include your change?

@moguls753
Copy link
Author

Hey @guru245,

I totally missed #1475—thanks for pointing it out! That PR switches over to the new Neovim ≥0.11 LSP API, while this one sticks with the classic

require('lspconfig').<server>.setup{…}

Given that many distros (for example, Ubuntu 25 LTS ships 0.9.5) still ship older Neovims, I think it makes sense to keep using the legacy API, which isn’t going away anytime soon. For me #1475 is working perfectly fine though.

What do you think?

@VlaDexa
Copy link
Contributor

VlaDexa commented Jun 29, 2025

I think that kickstart supports only the latest stable, and should stick with that

@moguls753
Copy link
Author

In that case, #1475 seems perfectly fine — I’ll close this PR. Thanks for the pointer!

@moguls753 moguls753 closed this Jun 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants