add ltex lsp

This commit is contained in:
Andrzej Stepien 2024-03-18 14:07:30 +01:00
parent f23ada5260
commit 54c845ab59
1 changed files with 151 additions and 152 deletions

View File

@ -1,172 +1,171 @@
return { -- LSP Configuration & Plugins return { -- LSP Configuration & Plugins
'neovim/nvim-lspconfig', "neovim/nvim-lspconfig",
dependencies = { dependencies = {
-- Automatically install LSPs and related tools to stdpath for neovim -- Automatically install LSPs and related tools to stdpath for neovim
'williamboman/mason.nvim', "williamboman/mason.nvim",
'williamboman/mason-lspconfig.nvim', "williamboman/mason-lspconfig.nvim",
'WhoIsSethDaniel/mason-tool-installer.nvim', "WhoIsSethDaniel/mason-tool-installer.nvim",
-- Useful status updates for LSP. -- Useful status updates for LSP.
-- NOTE: `opts = {}` is the same as calling `require('fidget').setup({})` -- NOTE: `opts = {}` is the same as calling `require('fidget').setup({})`
{ 'j-hui/fidget.nvim', opts = {} }, { "j-hui/fidget.nvim", opts = {} },
-- `neodev` configures Lua LSP for your Neovim config, runtime and plugins -- `neodev` configures Lua LSP for your Neovim config, runtime and plugins
-- used for completion, annotations and signatures of Neovim apis -- used for completion, annotations and signatures of Neovim apis
{ 'folke/neodev.nvim', opts = {} }, { "folke/neodev.nvim", opts = {} },
}, },
config = function() config = function()
-- This function gets run when an LSP attaches to a particular buffer.
-- That is to say, every time a new file is opened that is associated with
-- an lsp (for example, opening `main.rs` is associated with `rust_analyzer`) this
-- function will be executed to configure the current buffer
vim.api.nvim_create_autocmd("LspAttach", {
group = vim.api.nvim_create_augroup("kickstart-lsp-attach", { clear = true }),
callback = function(event)
-- NOTE: Remember that lua is a real programming language, and as such it is possible
-- to define small helper and utility functions so you don't have to repeat yourself
-- many times.
--
-- In this case, we create a function that lets us more easily define mappings specific
-- for LSP related items. It sets the mode, buffer and description for us each time.
local map = function(keys, func, desc)
vim.keymap.set("n", keys, func, { buffer = event.buf, desc = "LSP: " .. desc })
end
-- This function gets run when an LSP attaches to a particular buffer. -- Jump to the definition of the word under your cursor.
-- That is to say, every time a new file is opened that is associated with -- This is where a variable was first declared, or where a function is defined, etc.
-- an lsp (for example, opening `main.rs` is associated with `rust_analyzer`) this -- To jump back, press <C-t>.
-- function will be executed to configure the current buffer map("gd", require("telescope.builtin").lsp_definitions, "[G]oto [D]efinition")
vim.api.nvim_create_autocmd('LspAttach', {
group = vim.api.nvim_create_augroup('kickstart-lsp-attach', { clear = true }),
callback = function(event)
-- NOTE: Remember that lua is a real programming language, and as such it is possible
-- to define small helper and utility functions so you don't have to repeat yourself
-- many times.
--
-- In this case, we create a function that lets us more easily define mappings specific
-- for LSP related items. It sets the mode, buffer and description for us each time.
local map = function(keys, func, desc)
vim.keymap.set('n', keys, func, { buffer = event.buf, desc = 'LSP: ' .. desc })
end
-- Jump to the definition of the word under your cursor. -- Find references for the word under your cursor.
-- This is where a variable was first declared, or where a function is defined, etc. map("gr", require("telescope.builtin").lsp_references, "[G]oto [R]eferences")
-- To jump back, press <C-t>.
map('gd', require('telescope.builtin').lsp_definitions, '[G]oto [D]efinition')
-- Find references for the word under your cursor. -- Jump to the implementation of the word under your cursor.
map('gr', require('telescope.builtin').lsp_references, '[G]oto [R]eferences') -- Useful when your language has ways of declaring types without an actual implementation.
map("gI", require("telescope.builtin").lsp_implementations, "[G]oto [I]mplementation")
-- Jump to the implementation of the word under your cursor. -- Jump to the type of the word under your cursor.
-- Useful when your language has ways of declaring types without an actual implementation. -- Useful when you're not sure what type a variable is and you want to see
map('gI', require('telescope.builtin').lsp_implementations, '[G]oto [I]mplementation') -- the definition of its *type*, not where it was *defined*.
map("<leader>D", require("telescope.builtin").lsp_type_definitions, "Type [D]efinition")
-- Jump to the type of the word under your cursor. -- Fuzzy find all the symbols in your current document.
-- Useful when you're not sure what type a variable is and you want to see -- Symbols are things like variables, functions, types, etc.
-- the definition of its *type*, not where it was *defined*. map("<leader>ds", require("telescope.builtin").lsp_document_symbols, "[D]ocument [S]ymbols")
map('<leader>D', require('telescope.builtin').lsp_type_definitions, 'Type [D]efinition')
-- Fuzzy find all the symbols in your current document. -- Fuzzy find all the symbols in your current workspace
-- Symbols are things like variables, functions, types, etc. -- Similar to document symbols, except searches over your whole project.
map('<leader>ds', require('telescope.builtin').lsp_document_symbols, '[D]ocument [S]ymbols') map("<leader>ws", require("telescope.builtin").lsp_dynamic_workspace_symbols, "[W]orkspace [S]ymbols")
-- Fuzzy find all the symbols in your current workspace -- Rename the variable under your cursor
-- Similar to document symbols, except searches over your whole project. -- Most Language Servers support renaming across files, etc.
map('<leader>ws', require('telescope.builtin').lsp_dynamic_workspace_symbols, '[W]orkspace [S]ymbols') map("<leader>rn", vim.lsp.buf.rename, "[R]e[n]ame")
-- Rename the variable under your cursor -- Execute a code action, usually your cursor needs to be on top of an error
-- Most Language Servers support renaming across files, etc. -- or a suggestion from your LSP for this to activate.
map('<leader>rn', vim.lsp.buf.rename, '[R]e[n]ame') map("<leader>ca", vim.lsp.buf.code_action, "[C]ode [A]ction")
-- Execute a code action, usually your cursor needs to be on top of an error -- Opens a popup that displays documentation about the word under your cursor
-- or a suggestion from your LSP for this to activate. -- See `:help K` for why this keymap
map('<leader>ca', vim.lsp.buf.code_action, '[C]ode [A]ction') map("K", vim.lsp.buf.hover, "Hover Documentation")
-- Opens a popup that displays documentation about the word under your cursor -- WARN: This is not Goto Definition, this is Goto Declaration.
-- See `:help K` for why this keymap -- For example, in C this would take you to the header
map('K', vim.lsp.buf.hover, 'Hover Documentation') map("gD", vim.lsp.buf.declaration, "[G]oto [D]eclaration")
-- WARN: This is not Goto Definition, this is Goto Declaration. -- The following two autocommands are used to highlight references of the
-- For example, in C this would take you to the header -- word under your cursor when your cursor rests there for a little while.
map('gD', vim.lsp.buf.declaration, '[G]oto [D]eclaration') -- See `:help CursorHold` for information about when this is executed
--
-- When you move your cursor, the highlights will be cleared (the second autocommand).
local client = vim.lsp.get_client_by_id(event.data.client_id)
if client and client.server_capabilities.documentHighlightProvider then
vim.api.nvim_create_autocmd({ "CursorHold", "CursorHoldI" }, {
buffer = event.buf,
callback = vim.lsp.buf.document_highlight,
})
-- The following two autocommands are used to highlight references of the vim.api.nvim_create_autocmd({ "CursorMoved", "CursorMovedI" }, {
-- word under your cursor when your cursor rests there for a little while. buffer = event.buf,
-- See `:help CursorHold` for information about when this is executed callback = vim.lsp.buf.clear_references,
-- })
-- When you move your cursor, the highlights will be cleared (the second autocommand). end
local client = vim.lsp.get_client_by_id(event.data.client_id) end,
if client and client.server_capabilities.documentHighlightProvider then })
vim.api.nvim_create_autocmd({ 'CursorHold', 'CursorHoldI' }, {
buffer = event.buf,
callback = vim.lsp.buf.document_highlight,
})
vim.api.nvim_create_autocmd({ 'CursorMoved', 'CursorMovedI' }, { -- LSP servers and clients are able to communicate to each other what features they support.
buffer = event.buf, -- By default, Neovim doesn't support everything that is in the LSP Specification.
callback = vim.lsp.buf.clear_references, -- When you add nvim-cmp, luasnip, etc. Neovim now has *more* capabilities.
}) -- So, we create new capabilities with nvim cmp, and then broadcast that to the servers.
end local capabilities = vim.lsp.protocol.make_client_capabilities()
end, capabilities = vim.tbl_deep_extend("force", capabilities, require("cmp_nvim_lsp").default_capabilities())
})
-- LSP servers and clients are able to communicate to each other what features they support. -- Enable the following language servers
-- By default, Neovim doesn't support everything that is in the LSP Specification. -- Feel free to add/remove any LSPs that you want here. They will automatically be installed.
-- When you add nvim-cmp, luasnip, etc. Neovim now has *more* capabilities. --
-- So, we create new capabilities with nvim cmp, and then broadcast that to the servers. -- Add any additional override configuration in the following tables. Available keys are:
local capabilities = vim.lsp.protocol.make_client_capabilities() -- - cmd (table): Override the default command used to start the server
capabilities = vim.tbl_deep_extend('force', capabilities, require('cmp_nvim_lsp').default_capabilities()) -- - filetypes (table): Override the default list of associated filetypes for the server
-- - capabilities (table): Override fields in capabilities. Can be used to disable certain LSP features.
-- - settings (table): Override the default settings passed when initializing the server.
-- For example, to see the options for `lua_ls`, you could go to: https://luals.github.io/wiki/settings/
local servers = {
-- clangd = {},
-- gopls = {},
-- pyright = {},
-- rust_analyzer = {},
-- ... etc. See `:help lspconfig-all` for a list of all the pre-configured LSPs
--
-- Some languages (like typescript) have entire language plugins that can be useful:
-- https://github.com/pmizio/typescript-tools.nvim
--
-- But for many setups, the LSP (`tsserver`) will work just fine
tsserver = {},
ltex = {}, --
-- Enable the following language servers lua_ls = {
-- Feel free to add/remove any LSPs that you want here. They will automatically be installed. -- cmd = {...},
-- -- filetypes { ...},
-- Add any additional override configuration in the following tables. Available keys are: -- capabilities = {},
-- - cmd (table): Override the default command used to start the server settings = {
-- - filetypes (table): Override the default list of associated filetypes for the server Lua = {
-- - capabilities (table): Override fields in capabilities. Can be used to disable certain LSP features. completion = {
-- - settings (table): Override the default settings passed when initializing the server. callSnippet = "Replace",
-- For example, to see the options for `lua_ls`, you could go to: https://luals.github.io/wiki/settings/ },
local servers = { -- You can toggle below to ignore Lua_LS's noisy `missing-fields` warnings
-- clangd = {}, -- diagnostics = { disable = { 'missing-fields' } },
-- gopls = {}, },
-- pyright = {}, },
-- rust_analyzer = {}, },
-- ... etc. See `:help lspconfig-all` for a list of all the pre-configured LSPs }
--
-- Some languages (like typescript) have entire language plugins that can be useful:
-- https://github.com/pmizio/typescript-tools.nvim
--
-- But for many setups, the LSP (`tsserver`) will work just fine
tsserver = {},
--
lua_ls = { -- Ensure the servers and tools above are installed
-- cmd = {...}, -- To check the current status of installed tools and/or manually install
-- filetypes { ...}, -- other tools, you can run
-- capabilities = {}, -- :Mason
settings = { --
Lua = { -- You can press `g?` for help in this menu
completion = { require("mason").setup()
callSnippet = 'Replace',
},
-- You can toggle below to ignore Lua_LS's noisy `missing-fields` warnings
-- diagnostics = { disable = { 'missing-fields' } },
},
},
},
}
-- Ensure the servers and tools above are installed -- You can add other tools here that you want Mason to install
-- To check the current status of installed tools and/or manually install -- for you, so that they are available from within Neovim.
-- other tools, you can run local ensure_installed = vim.tbl_keys(servers or {})
-- :Mason vim.list_extend(ensure_installed, {
-- "stylua", -- Used to format lua code
-- You can press `g?` for help in this menu })
require('mason').setup() require("mason-tool-installer").setup({ ensure_installed = ensure_installed })
-- You can add other tools here that you want Mason to install require("mason-lspconfig").setup({
-- for you, so that they are available from within Neovim. handlers = {
local ensure_installed = vim.tbl_keys(servers or {}) function(server_name)
vim.list_extend(ensure_installed, { local server = servers[server_name] or {}
'stylua', -- Used to format lua code -- This handles overriding only values explicitly passed
}) -- by the server configuration above. Useful when disabling
require('mason-tool-installer').setup { ensure_installed = ensure_installed } -- certain features of an LSP (for example, turning off formatting for tsserver)
server.capabilities = vim.tbl_deep_extend("force", {}, capabilities, server.capabilities or {})
require('mason-lspconfig').setup { require("lspconfig")[server_name].setup(server)
handlers = { end,
function(server_name) },
local server = servers[server_name] or {} })
-- This handles overriding only values explicitly passed end,
-- by the server configuration above. Useful when disabling }
-- certain features of an LSP (for example, turning off formatting for tsserver)
server.capabilities = vim.tbl_deep_extend('force', {}, capabilities, server.capabilities or {})
require('lspconfig')[server_name].setup(server)
end,
},
}
end,
}