Fixing LSP configuration version #13
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated various configuration settings and plugin versions in init.lua.
Fix LSP configuration version detection typo
Summary
- Fixed typo in Neovim version check that was causing LSP configuration to use deprecated API
- Changed nvim1.11 to nvim-0.11 in version detection
Problem
The configuration was checking for 'nvim1.11' instead of 'nvim-0.11', causing the version
detection to always fail. This resulted in the code always falling back to the deprecated
require('lspconfig') API, even on Neovim 0.11+, which triggered deprecation warnings.
Solution
Corrected the version string in init.lua:586 to properly detect Neovim 0.11+ and use the modern
vim.lsp.config API.
Changes
- init.lua:586 - Fixed version check from 'nvim1.11' to 'nvim-0.11'
Testing
- Verified deprecation warning no longer appears on Neovim 0.11+
- LSP servers load correctly using the modern API
Modify Neovim configuration and plugin versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix LSP configuration version detection typo
Summary
Problem
The configuration was checking for 'nvim1.11' instead of 'nvim-0.11', causing the version
detection to always fail. This resulted in the code always falling back to the deprecated
require('lspconfig') API, even on Neovim 0.11+, which triggered deprecation warnings.
Solution
Corrected the version string in init.lua:586 to properly detect Neovim 0.11+ and use the modern
vim.lsp.config API.
Changes
Testing