vh/kickstart.nvim
1
0
Fork 0
mirror of https://github.com/nvim-lua/kickstart.nvim.git synced 2026-10-15 23:19:54 -07:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update the docs about lua_ls

Browse Source
This commit is contained in:
orip
2026-10-06 00:47:39 +03:00
parent 2e8d67c328
commit 8eba8d5079
2 changed files with 2 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
init.lua
+2 -2
View File
@@ -639,7 +639,7 @@ do
-- 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`, `emmylua_ls`, `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!
--
@@ -790,7 +790,7 @@ do
-- Automatically install LSPs and related tools to stdpath for Neovim
require('mason').setup {}
-- Translates between nvim-lspconfig server names and mason.nvim package names (e.g. lua_ls <-> lua-language-server)
-- Translates between nvim-lspconfig server names and mason.nvim package names (e.g. yaml_ls <-> yaml-language-server)
require('mason-lspconfig').setup {
automatic_enable = false, -- Change this to true if you want to automatically enable servers that are installed manually (e.g. via :Mason / :MasonInstall)
}