feat: add support for new LSP config API in Neovim 0.11+ #1475

umutondersu · 2025-04-16T17:39:11Z

Summary

Added support for the new LSP configuration API introduced in Neovim 0.11+
Updated Mason version to v2

ro0gr · 2025-04-17T10:28:39Z

Kickstart.nvim targets only the latest 'stable' and latest 'nightly' of Neovim.

Do we really need backward compatibility with Neovim 0 10? I'd consider going with a lighter, happy-path solution. Since the project mainly targets newcomers and servers educational purposes, they'd likely prefer to avoid dealing with legacy approaches.

umutondersu · 2025-04-17T11:08:05Z

I think that would be the right approach as well. The reason I intended to maintain backwards compatibility is that some parts of the code is still trying to maintain 0.10 like the client_supports_method. Depending on the others reaction I would also be in favor of removing it.

umutondersu · 2025-04-17T12:44:00Z

There is also the problem new syntax not supporting all lsp configs. For example tailwindcss requires the old setup. Could be a good idea to delay this until most lsp configs migrate.

nickgnd · 2025-04-17T13:18:51Z

Hey everyone 👋
I remember a few related conversations that happen lately on this topic, let me share them here

#1458
#1331

I hope they can be useful, cheers ✌️

init.lua

umutondersu · 2025-04-17T15:14:56Z

Hey everyone 👋 I remember a few related conversations that happen lately on this topic, let me share them here

#1458 #1331

I hope they can be useful, cheers ✌️

This setup config does not clash with blink.cmp so in that sense It should be okay.
I would be able to support this in an ongoing basis
I think using the native way would provide a better experience for newbies but that's up to debate

Signed-off-by: Umut Sahin Onder <[email protected]>

kaezrr · 2025-04-20T04:41:56Z

In my opinion, we shouldn't bother with backwards compatibility since Kickstart is mostly aimed at beginners who will download the latest version of Neovim as per the instructions in the repo readme

umutondersu · 2025-04-20T11:06:46Z

I have removed backwards compatibility and added useful comments for LSPs that still require the old setup

init.lua

umutondersu · 2025-04-24T10:18:55Z

Messing around with this and found that this will not respect the lsp_format = "fallback" option in the conform.nvim config. To replicate:
1. comment out the stylua formatter line from conform.nvim config

2. save and reload neovim

3. overindent a line or any other formatting change

4. write file
For me it did not fallback on the lua_ls server for formatting.

I couldn't replicate the issue. I do not think it would be related to these changes as conform.nvim does not use an LSP. In any case If you could check your conform logs by using :ConformInfo It could reveal more info about the issue.

init.lua

Co-authored-by: Rory Hendrickson <[email protected]>

- nvim-lua/kickstart.nvim#1475

init.lua

pandar00 · 2025-05-10T08:28:29Z

AFAIK mason-lspconfig setting's handler is a no-op. (PR)
LSP settings are moved to after/lsp/<lang_server_name>.lua (credit; in JP)
lsp-config doc also explains the config is merged with the default.

Note: The merge semantics of configurations follow the behaviour of vim.tbl_deep_extend().

I've been updating my old neovim configs with the latest kickstart but the LSP settings weren't reflected in :LspInfo, but after following the above, LSP correctly reads them

umutondersu · 2025-05-10T17:09:12Z

AFAIK mason-lspconfig setting's handler is a no-op. (PR) LSP settings are moved to after/lsp/<lang_server_name>.lua (credit; in JP) lsp-config doc also explains the config is merged with the default.

Note: The merge semantics of configurations follow the behaviour of vim.tbl_deep_extend().

I've been updating my old neovim configs with the latest kickstart but the LSP settings weren't reflected in :LspInfo, but after following the above, LSP correctly reads them

If we were to move LSP configs to their own file, I don't know how mason-tool-installer would work without the servers table maybe by iterating over file names?

In your config I see that you still have the servers table. If It is still gonna be preset wouldn't be better to use vim.lsp.config with a loop (like my first hunk) rather than having 2 separate places for LSP servers?

umutondersu · 2025-05-10T17:13:46Z

As mentioned in previous conversations, Mason v2 has started introducing a significant delay during startup. For now, I’ve pinned the Mason version to avoid this issue.

From my testing, the problem appears to be related to mason-tool-installer; without it, I don’t experience any delays. It would be helpful to hear from someone with more insight into this before proceeding further with Mason v2.

guru245 · 2025-06-01T14:08:07Z

Hi @spundun ,

Neovim also provides a prebuilt package: AppImage and tarball. We don't have to build Neovim for the distrubution. Please check out this link: https://github.com/neovim/neovim/releases/tag/v0.11.2

spundun · 2025-06-01T17:59:34Z

Hi @guru245 , Thanks for the response. That's a cool new thing I learned today :).

The README.md just says "If you are experiencing issues, please make sure you have the latest versions.". Since kickstart puts priority on being new-user-friendly, I'd suggest you add more detailed guidelines there. To many users, "make sure you have the latest version" might just mean making sure you have all the latest software updates from your package manager, especially if you're on the latest version of some standard OS.

Maybe adding detailed instructions along the lines... if nvim --version reports a version lower than the Required version then here are the instructions on how to install it in the user-file-system and set it as your editor before you begin.

Based on nvim-lua#1475

handlers has been removed in v2: https://github.com/mason-org/mason-lspconfig.nvim/blob/main/CHANGELOG.md#200-2025-05-06 Watch this PR: nvim-lua/kickstart.nvim#1475

See nvim-lua#1475

mybuddymichael · 2025-07-01T17:16:01Z

I spent way too long trying to figure out why inlay hints wouldn't appear anywhere! Turns out my LSP settings weren't even being loaded. I'm super glad I found this PR!

Based on nvim-lua#1475

Based on PR nvim-lua#1475 : feat: add support for new LSP config API in Neovim 0.11+ link : nvim-lua#1475

nvim-lua#1475

ref: nvim-lua#1475 nvim-lua#1475

* Only use pylint as the pylsp's linter. ref: nvim-lua#1475 nvim-lua#1475

Ktsierra · 2025-07-23T17:09:37Z

any updates on this pr? the current implementation of mson-lspconfig doesn't work, handlers was removed in V2.

Based off this kickstart.nvim PR: nvim-lua/kickstart.nvim#1475

nvim-lua/kickstart.nvim#1475

Based on nvim-lua#1475

logrusx · 2025-08-03T17:15:35Z

I recommend #1663 over this PR.

It states clearly what it does, it does it correctly and stays to the point.

This one is actually dealing with mason-lspconfig 2.0, rather than nvim 0.11, does more than it says and pushes authors preferences.

logrusx · 2025-08-03T18:19:08Z

init.lua

+      ---@type MasonLspconfigSettings
+      ---@diagnostic disable-next-line: missing-fields
+      require('mason-lspconfig').setup {
+        automatic_enable = vim.tbl_keys(servers or {}),


Despite that , I still prefer declarativly specifying all the LSPs in the config file, instead of downloading them using the mason interface. This way I can commit those LSPs and have a reproducible setup. This is the same reason I commit the lazy-lock.json file.

This is unacceptable for plugins that need to set additional settings before the LSP is setup. For one - nvim-java for jdtls. It is also absolutely unnecessary.

Pushing your preferences into a public repository is not very kind to others with different preferences.

I find #1663 better than this one.

NaniNoni · 2025-08-13T19:37:18Z

Is there anything major preventing this from being merged? I merged this patchset into my personal config and everything works fine.

umutondersu added 2 commits April 16, 2025 19:34

feat: add support for new LSP config API in Neovim 0.11+

3f0cd75

Typo fix

f70dcb3

yetyetanotherusername reviewed Apr 17, 2025

View reviewed changes

init.lua Outdated Show resolved Hide resolved

init.lua Outdated Show resolved Hide resolved

umutondersu added 2 commits April 17, 2025 17:17

fix(lsp): correct variable name in lsp config loop

4b81900

Signed-off-by: Umut Sahin Onder <[email protected]>

style: format with stylua

5502cea

fix(lsp): Remove backwards compatibility and add comments for lsp setup

a590ab6

umutondersu added 2 commits April 20, 2025 13:12

fix: Typo in comment

dac395d

fix: revert back to original handler logic

531073d

1Naim reviewed Apr 22, 2025

View reviewed changes

init.lua Outdated Show resolved Hide resolved

yetyetanotherusername approved these changes Apr 23, 2025

View reviewed changes

This comment was marked as resolved.

Sign in to view

This comment has been minimized.

Sign in to view

roryhen reviewed Apr 27, 2025

View reviewed changes

init.lua Outdated Show resolved Hide resolved

oriori1703 mentioned this pull request Apr 29, 2025

Replace outdated require('lspconfig')[server_name].setup() #1502

Open

Fix: correct variables inside comments

81c5210

Co-authored-by: Rory Hendrickson <[email protected]>

michaellisitsa added a commit to michaellisitsa/dotfiles that referenced this pull request May 5, 2025

Use neovim v0.11 lsp capabilities

e917ad0

- nvim-lua/kickstart.nvim#1475

1Naim reviewed May 7, 2025

View reviewed changes

init.lua Outdated Show resolved Hide resolved

1Naim reviewed May 7, 2025

View reviewed changes

init.lua Outdated Show resolved Hide resolved

fix(deps): pin mason plugin versions to v1.*

9e0c7b6

Mithrandir2k18 mentioned this pull request Jun 2, 2025

[docs] Document all sane ways to get the latest stable neovim release in the README #1583

Open

nickgnd added a commit to nickgnd/kickstart.nvim that referenced this pull request Jun 3, 2025

chore: use new LSP config from nvim 0.11

981034a

Based on nvim-lua#1475

149segolte added a commit to 149segolte/nvim that referenced this pull request Jun 4, 2025

Patch PR nvim-lua#1475 from upstream for LSP configs

b14c245

kartikvashistha mentioned this pull request Jun 7, 2025

feat: improved lsp setup for nvim > 0.11 #1590

Open

This was referenced Jun 10, 2025

[Feature request]: ability to configure root_markers for lsp #1592

Open

Feature/snacks picker #1481

Open

SetsuikiHyoryu mentioned this pull request Jun 11, 2025

I don't think lspconfig setup handlers are being called #1595

Open

brycewalkerdev added a commit to brycewalkerdev/nvim-config that referenced this pull request Jun 13, 2025

fixed lspconfig not configuring language servers (nvim-lua#1475)

5629288

guru245 mentioned this pull request Jun 27, 2025

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

Closed

ranger-ross added a commit to ranger-ross/kickstart.nvim that referenced this pull request Jun 29, 2025

fixed mason lspconfig

96e7221

See nvim-lua#1475

SetsuikiHyoryu mentioned this pull request Jul 1, 2025

:e % + tab does not expand #1622

Closed

1 task

oriori1703 added a commit to oriori1703/kickstart-modular.nvim that referenced this pull request Jul 4, 2025

add support for new LSP config API in Neovim 0.11+

55bd808

Based on nvim-lua#1475

csahid added a commit to csahid/kickstart.nvim that referenced this pull request Jul 9, 2025

feat: adjust mason v2

acdd701

Based on PR nvim-lua#1475 : feat: add support for new LSP config API in Neovim 0.11+ link : nvim-lua#1475

nmosim pushed a commit to nmosim/kickstart-modular.nvim that referenced this pull request Jul 18, 2025

Fix: LSP configuration not loaded (see nvim-lua#1475)

fd918c4

JPHarding added a commit to JPHarding/jph.kickstart.nvim that referenced this pull request Jul 18, 2025

nvim-lua#1475 Fix for server settings not doing anything.

ceb43df

nvim-lua#1475

umutondersu requested a review from carloscalla July 19, 2025 21:49

andychi117 added a commit to andychi117/kickstart.nvim that referenced this pull request Jul 22, 2025

fix: Setting LSP config correctly.

1bcacbf

ref: nvim-lua#1475 nvim-lua#1475

andychi117 added a commit to andychi117/kickstart.nvim that referenced this pull request Jul 22, 2025

fix: Setting LSP config correctly.

fdacca8

* Only use pylint as the pylsp's linter. ref: nvim-lua#1475 nvim-lua#1475

metamorfoso pushed a commit to metamorfoso/nvim that referenced this pull request Jul 24, 2025

Update to use new LSP configuration API in neovim v0.11+

ef49a17

Based off this kickstart.nvim PR: nvim-lua/kickstart.nvim#1475

tomasgareau added a commit to tomasgareau/nvim that referenced this pull request Jul 28, 2025

TEMP: manually apply nvim-lua/kickstart.nvim#1475

9c99c4e

nvim-lua/kickstart.nvim#1475

kojdm added a commit to kojdm/kickstart-modular.nvim that referenced this pull request Jul 30, 2025

Fix lspconfig

cd8e53b

Based on nvim-lua#1475

Ktsierra mentioned this pull request Aug 1, 2025

fix(lsp): updated config for mason to v2 #1663

Open

logrusx reviewed Aug 3, 2025

View reviewed changes

feat: add support for new LSP config API in Neovim 0.11+ #1475

Are you sure you want to change the base?

feat: add support for new LSP config API in Neovim 0.11+ #1475

Conversation

umutondersu commented Apr 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Uh oh!

ro0gr commented Apr 17, 2025

Uh oh!

umutondersu commented Apr 17, 2025

Uh oh!

umutondersu commented Apr 17, 2025

Uh oh!

nickgnd commented Apr 17, 2025

Uh oh!

Uh oh!

Uh oh!

umutondersu commented Apr 17, 2025

Uh oh!

kaezrr commented Apr 20, 2025

Uh oh!

umutondersu commented Apr 20, 2025

Uh oh!

Uh oh!

This comment was marked as resolved.

umutondersu commented Apr 24, 2025

Uh oh!

This comment has been minimized.

Uh oh!

Uh oh!

Uh oh!

pandar00 commented May 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

umutondersu commented May 10, 2025

Uh oh!

umutondersu commented May 10, 2025

Uh oh!

guru245 commented Jun 1, 2025

Uh oh!

spundun commented Jun 1, 2025

Uh oh!

mybuddymichael commented Jul 1, 2025

Uh oh!

Ktsierra commented Jul 23, 2025

Uh oh!

logrusx commented Aug 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

logrusx Aug 3, 2025

Choose a reason for hiding this comment

Uh oh!

NaniNoni commented Aug 13, 2025

Uh oh!

Uh oh!

umutondersu commented Apr 16, 2025 •

edited

Loading

pandar00 commented May 10, 2025 •

edited

Loading

logrusx commented Aug 3, 2025 •

edited

Loading