Update LSP server name from lua_ls to lua-language-server
This commit is contained in:
parent
e8378d3b79
commit
c11ac53f28
6
init.lua
6
init.lua
|
|
@ -498,7 +498,7 @@ require('lazy').setup({
|
|||
-- and language tooling communicate in a standardized fashion.
|
||||
--
|
||||
-- In general, you have a "server" which is some tool built to understand a particular
|
||||
-- language (such as `gopls`, `lua_ls`, `rust_analyzer`, etc.). These Language Servers
|
||||
-- language (such as `gopls`, `lua-language-server`, `rust_analyzer`, etc.). These Language Servers
|
||||
-- (sometimes called LSP servers, but that's kind of like ATM Machine) are standalone
|
||||
-- processes that communicate with some "client" - in this case, Neovim!
|
||||
--
|
||||
|
|
@ -628,7 +628,7 @@ require('lazy').setup({
|
|||
end
|
||||
|
||||
-- Special Lua Config, as recommended by neovim help docs
|
||||
vim.lsp.config('lua_ls', {
|
||||
vim.lsp.config('lua-language-server', {
|
||||
on_init = function(client)
|
||||
if client.workspace_folders then
|
||||
local path = client.workspace_folders[1].name
|
||||
|
|
@ -652,7 +652,7 @@ require('lazy').setup({
|
|||
Lua = {},
|
||||
},
|
||||
})
|
||||
vim.lsp.enable 'lua_ls'
|
||||
vim.lsp.enable 'lua-language-server'
|
||||
end,
|
||||
},
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue