Skip to content

Replace deprecated vim.lsp.buf_get_clients with vim.lsp.get_clients #91

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

milanfusco
Copy link

Neovim has deprecated the use of vim.lsp.buf_get_clients() in favor of vim.lsp.get_clients(), and this change removes the deprecation warning triggered by lsp-status.nvim. Updating to the new API helps ensure compatibility with future Neovim releases (e.g., 0.12 and later).

Changes:

  • Replaced all occurrences of vim.lsp.buf_get_clients() with vim.lsp.get_clients() in the lsp-status plugin (in statusline.lua and other related modules).
  • Verified that the new function correctly returns the active LSP clients, maintaining existing functionality.
  • Tested with NVIM v0.11.0-dev-736+g648d6426c (RelWithDebInfo build, LuaJIT 2.1.1724512491)
  • Confirmed that deprecation warnings are no longer emitted during startup.

Neovim has deprecated the use of vim.lsp.buf_get_clients() in favor of
vim.lsp.get_clients(), and this change removes the deprecation warning
triggered by lsp-status.nvim. Updating to the new API helps ensure
compatibility with future Neovim releases (e.g., 0.12 and later).

Changes:
- Replaced all occurrences of vim.lsp.buf_get_clients() with vim.lsp.get_clients()
  in the lsp-status plugin (in statusline.lua and other related modules).
- Verified that the new function correctly returns the active LSP clients,
  maintaining existing functionality.
- Tested with NVIM v0.11.0-dev-736+g648d6426c (RelWithDebInfo build, LuaJIT 2.1.1724512491)
- Confirmed that deprecation warnings are no longer emitted during startup.
@svanharmelen
Copy link

@tjdevries any chance we can get this in? Or do you recommend we stop using this plugin (hope not)?

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.

2 participants