Movatterモバイル変換


[0]ホーム

URL:


Lsp

Nvim:help pages,generated fromsource using thetree-sitter-vimdoc parser.


LSP client/frameworkLSP
Nvim supports the Language Server Protocol (LSP), which means it acts asa client to LSP servers and includes a Lua frameworkvim.lsp for buildingenhanced LSP tools.
https://microsoft.github.io/language-server-protocol/
LSP facilitates features like go-to-definition, find references, hover,completion, rename, format, refactor, etc., using semantic whole-projectanalysis (unlikectags).

QUICKSTARTlsp-quickstart

Nvim provides an LSP client, but the servers are provided by third parties.Follow these steps to get LSP features:
1. Install language servers using your package manager or by following the upstream installation instructions. You can find language servers here:https://microsoft.github.io/language-server-protocol/implementors/servers/
2. Usevim.lsp.config() to define a configuration for an LSP client. Example:
vim.lsp.config['luals'] = {  -- Command and arguments to start the server.  cmd = { 'lua-language-server' },  -- Filetypes to automatically attach to.  filetypes = { 'lua' },  -- Sets the "root directory" to the parent directory of the file in the  -- current buffer that contains either a ".luarc.json" or a  -- ".luarc.jsonc" file. Files that share a root directory will reuse  -- the connection to the same LSP server.  -- Nested lists indicate equal priority, see |vim.lsp.Config|.  root_markers = { { '.luarc.json', '.luarc.jsonc' }, '.git' },  -- Specific settings to send to the server. The schema for this is  -- defined by the server. For example the schema for lua-language-server  -- can be found here https://raw.githubusercontent.com/LuaLS/vscode-lua/master/setting/schema.json  settings = {    Lua = {      runtime = {        version = 'LuaJIT',      }    }  }}
3. Usevim.lsp.enable() to enable a configuration. Example:
vim.lsp.enable('luals')
4. Restart Nvim, or use ":edit" to reload the buffer.
5. Check that LSP is active ("attached") for the buffer:
:checkhealth vim.lsp
6. (Optional) Configure keymaps and autocommands to use LSP features.lsp-attach

DEFAULTSlsp-defaults

When the Nvim LSP client starts it enables diagnosticsvim.diagnostic (seevim.diagnostic.config() to customize). It also sets various default options,listed below, if (1) the language server supports the functionality and (2)the options are empty or were set by the builtin runtime (ftplugin) files. Theoptions are not restored when the LSP client is stopped or detached.

BUFFER-LOCAL DEFAULTS

'omnifunc' is set tovim.lsp.omnifunc(), usei_CTRL-X_CTRL-O to trigger completion.
'tagfunc' is set tovim.lsp.tagfunc(). This enables features like go-to-definition,:tjump, and keymaps likeCTRL-],CTRL-W_],CTRL-W_} to utilize the language server.
'formatexpr' is set tovim.lsp.formatexpr(), so you can format lines viagq if the language server supports it.
To opt out of this usegw instead of gq, or clear'formatexpr' onLspAttach.
K is mapped tovim.lsp.buf.hover() unless'keywordprg' is customized or a custom keymap forK exists.

GLOBAL DEFAULTS

grrgragrngrii_CTRL-SThese GLOBAL keymaps are created unconditionally when Nvim starts:
"grn" is mapped in Normal mode tovim.lsp.buf.rename()
"gra" is mapped in Normal and Visual mode tovim.lsp.buf.code_action()
"grr" is mapped in Normal mode tovim.lsp.buf.references()
"gri" is mapped in Normal mode tovim.lsp.buf.implementation()
"gO" is mapped in Normal mode tovim.lsp.buf.document_symbol()
CTRL-S is mapped in Insert mode tovim.lsp.buf.signature_help()
You can remove GLOBAL keymaps at any time usingvim.keymap.del() or:unmap. See alsogr-default.
lsp-defaults-disable
To remove or override BUFFER-LOCAL defaults, define aLspAttach handler:
vim.api.nvim_create_autocmd('LspAttach', {  callback = function(args)    -- Unset 'formatexpr'    vim.bo[args.buf].formatexpr = nil    -- Unset 'omnifunc'    vim.bo[args.buf].omnifunc = nil    -- Unmap K    vim.keymap.del('n', 'K', { buffer = args.buf })  end,})

CONFIGlsp-config

You can configure LSP behavior statically via vim.lsp.config(), anddynamically vialsp-attach orClient:on_attach().
Usevim.lsp.config() to define, and selectively enable, LSP configurations.This is basically a wrapper aroundvim.lsp.start() which allows you to shareand merge configs (which may be provided by Nvim or third-party plugins).
When an LSP client starts, it resolves its configuration by merging from thefollowing (in increasing priority):
1. Configuration defined for the'*' name.2. Configuration from the result of merging all tables returned bylsp/<name>.lua files in'runtimepath' for a server of namename.3. Configurations defined anywhere else.
Note: The merge semantics of configurations follow the behaviour ofvim.tbl_deep_extend().
Example: given the following configs...
-- Defined in init.luavim.lsp.config('*', {  capabilities = {    textDocument = {      semanticTokens = {        multilineTokenSupport = true,      }    }  },  root_markers = { '.git' },})-- Defined in <rtp>/lsp/clangd.luareturn {  cmd = { 'clangd' },  root_markers = { '.clangd', 'compile_commands.json' },  filetypes = { 'c', 'cpp' },}-- Defined in init.luavim.lsp.config('clangd', {  filetypes = { 'c' },})
...the merged result is:
{  -- From the clangd configuration in <rtp>/lsp/clangd.lua  cmd = { 'clangd' },  -- From the clangd configuration in <rtp>/lsp/clangd.lua  -- Overrides the "*" configuration in init.lua  root_markers = { '.clangd', 'compile_commands.json' },  -- From the clangd configuration in init.lua  -- Overrides the clangd configuration in <rtp>/lsp/clangd.lua  filetypes = { 'c' },  -- From the "*" configuration in init.lua  capabilities = {    textDocument = {      semanticTokens = {        multilineTokenSupport = true,      }    }  }}
lsp-attach
To use LSP features beyond those provided by Nvim (seelsp-buf), you can setkeymaps and options onClient:on_attach() orLspAttach. Not all languageservers provide the same capabilities; checksupports_method() in yourLspAttach handler.lsp-lintlsp-formatExample: Enable auto-completion and auto-formatting ("linting"):
vim.api.nvim_create_autocmd('LspAttach', {  group = vim.api.nvim_create_augroup('my.lsp', {}),  callback = function(args)    local client = assert(vim.lsp.get_client_by_id(args.data.client_id))    if client:supports_method('textDocument/implementation') then      -- Create a keymap for vim.lsp.buf.implementation ...    end    -- Enable auto-completion. Note: Use CTRL-Y to select an item. |complete_CTRL-Y|    if client:supports_method('textDocument/completion') then      -- Optional: trigger autocompletion on EVERY keypress. May be slow!      -- local chars = {}; for i = 32, 126 do table.insert(chars, string.char(i)) end      -- client.server_capabilities.completionProvider.triggerCharacters = chars      vim.lsp.completion.enable(true, client.id, args.buf, {autotrigger = true})    end    -- Auto-format ("lint") on save.    -- Usually not needed if server supports "textDocument/willSaveWaitUntil".    if not client:supports_method('textDocument/willSaveWaitUntil')        and client:supports_method('textDocument/formatting') then      vim.api.nvim_create_autocmd('BufWritePre', {        group = vim.api.nvim_create_augroup('my.lsp', {clear=false}),        buffer = args.buf,        callback = function()          vim.lsp.buf.format({ bufnr = args.buf, id = client.id, timeout_ms = 1000 })        end,      })    end  end,})
To see the capabilities for a given server, try this in a LSP-enabled buffer:
:lua =vim.lsp.get_clients()[1].server_capabilities

FAQlsp-faq

Q: How to force-reload LSP?
A: Stop all clients, then reload the buffer.
:lua vim.lsp.stop_client(vim.lsp.get_clients()):edit
Q: Why isn't completion working?
A: In the buffer where you want to use LSP, check that'omnifunc' is set to "v:lua.vim.lsp.omnifunc"::verbose set omnifunc?
Some other plugin may be overriding the option. To avoid that you could set the option in anafter-directory ftplugin, e.g. "after/ftplugin/python.vim".
Q: How do I run a request synchronously (e.g. for formatting on file save)?
A: Check if the function has anasync parameter and set the value to false. E.g. code formatting:
" Auto-format *.rs (rust) files prior to saving them" (async = false is the default for format)autocmd BufWritePre *.rs lua vim.lsp.buf.format({ async = false })
lsp-vs-treesitter
Q: How do LSP and Treesitter compare?
A: LSP requires a client and language server. The language server uses semantic analysis to understand code at a project level. This provides language servers with the ability to rename across files, find definitions in external libraries and more.
treesitter is a language parsing library that provides excellent tools for incrementally parsing text and handling errors. This makes it a great fit for editors to understand the contents of the current file for things like syntax highlighting, simple goto-definitions, scope analysis and more.

LSP APIlsp-api

Thelsp-core API provides core functions for creating and managing clients.Thelsp-buf functions perform operations for LSP clients attached to thecurrent buffer.
lsp-method
Requests and notifications defined by the LSP specification are referred to as"LSP methods". These are handled by Lualsp-handler functions.
Thevim.lsp.handlers global table defines default handlers (only forserver-to-client requests/notifications, not client-to-server). Note: dependson server support; they won't run if your server doesn't support them.
You can list them with:
:lua vim.print(vim.tbl_keys(vim.lsp.handlers))
They are also listed below.
'callHierarchy/incomingCalls'
'callHierarchy/outgoingCalls'
'client/registerCapability'
'client/unregisterCapability'
'signature_help'
'textDocument/codeLens'
'textDocument/completion'
'textDocument/diagnostic'
'textDocument/documentHighlight'
'textDocument/documentSymbol'
'textDocument/formatting'
'textDocument/hover'
'textDocument/inlayHint'
'textDocument/publishDiagnostics'
'textDocument/rangeFormatting'
'textDocument/rename'
'textDocument/signatureHelp'
'typeHierarchy/subtypes'
'typeHierarchy/supertypes'
'window/logMessage'
'window/showDocument'
'window/showMessage'
'window/showMessageRequest'
'window/workDoneProgress/create'
'workspace/applyEdit'
'workspace/configuration'
'workspace/executeCommand'
'workspace/inlayHint/refresh'
'workspace/semanticTokens/refresh'
'workspace/symbol'
'workspace/workspaceFolders'
lsp-handler
LSP handlers are functions that handlelsp-responses to requests made by Nvimto the server. (Notifications, as opposed to requests, are fire-and-forget:there is no response, so they can't be handled.lsp-notification)
Each response handler has this signature:
function(err, result, ctx)
Parameters:
{err} (table|nil) Error info dict, ornil if the request completed.
{result} (Result|Params|nil)result key of thelsp-response ornil if the request failed.
{ctx} (table) Table of calling state associated with the handler, with these keys:
{method} (string)lsp-method name.
{client_id} (number)vim.lsp.Client identifier.
{bufnr} (Buffer) Buffer handle.
{params} (table|nil) Request parameters table.
{version} (number) Document version at time of request. Handlers can compare this to the current document version to check if the response is "stale". See alsob:changedtick.
Returns:
Two valuesresult, err whereerr is shaped like an RPC error:
{ code, message, data? }
You can usevim.lsp.rpc.rpc_response_error() to create this object.
lsp-handler-resolution
Handlers can be set by (in increasing priority):
vim.lsp.handlers
Directly calling a LSP method viaClient:request(). This is the only way to "override" the default client-to-server request handling (by side-steppingvim.lsp.buf and related interfaces).
local client = assert(vim.lsp.get_clients()[1])client:request('textDocument/definition')
Setting a field invim.lsp.handlers. This global table contains the default mappings oflsp-method names to handlers. (Note: only for server-to-client requests/notifications, not client-to-server.) Example:
vim.lsp.handlers['textDocument/publishDiagnostics'] = my_custom_diagnostics_handler
Passing a{handlers} parameter tovim.lsp.start(). This sets the defaultlsp-handler for a specific server. (Note: only for server-to-client requests/notifications, not client-to-server.) Example:
vim.lsp.start {  ..., -- Other configuration omitted.  handlers = {    ['textDocument/publishDiagnostics'] = my_custom_diagnostics_handler  },}
Passing a{handler} parameter tovim.lsp.buf_request_all(). This sets thelsp-handler ONLY for the given request(s). Example:
vim.lsp.buf_request_all(  0,  'textDocument/publishDiagnostics',  my_request_params,  my_handler)
vim.lsp.log_levels
Log levels are defined invim.log.levels

VIM.LSP.PROTOCOLvim.lsp.protocol

Modulevim.lsp.protocol defines constants dictated by the LSP specification,and helper functions for creating protocol-related objects.https://github.com/microsoft/language-server-protocol/raw/gh-pages/_specifications/specification-3-14.md
For examplevim.lsp.protocol.ErrorCodes allows reverse lookup by number orname:
vim.lsp.protocol.TextDocumentSyncKind.Full == 1vim.lsp.protocol.TextDocumentSyncKind[1] == "Full"
lsp-response
LSP response shape:https://microsoft.github.io/language-server-protocol/specifications/specification-current/#responseMessage
lsp-notification
LSP notification shape:https://microsoft.github.io/language-server-protocol/specifications/specification-current/#notificationMessage

LSP HIGHLIGHTlsp-highlight

Reference Highlights:
Highlight groups that are meant to be used byvim.lsp.buf.document_highlight().
You can see more about the differences in types here:https://microsoft.github.io/language-server-protocol/specification#textDocument_documentHighlight
hl-LspReferenceText
LspReferenceText used for highlighting "text" referenceshl-LspReferenceRead
LspReferenceRead used for highlighting "read" referenceshl-LspReferenceWrite
LspReferenceWrite used for highlighting "write" referenceshl-LspReferenceTarget
LspReferenceTarget used for highlighting reference targets (e.g. in a hover range)hl-LspInlayHint
LspInlayHint used for highlighting inlay hints
lsp-highlight-codelens
Highlight groups related tolsp-codelens functionality.
hl-LspCodeLens
LspCodeLens Used to color the virtual text of the codelens. Seenvim_buf_set_extmark().
LspCodeLensSeparatorhl-LspCodeLensSeparator
Used to color the separator between two or more code lenses.
lsp-highlight-signature
Highlight groups related tovim.lsp.handlers.signature_help().
hl-LspSignatureActiveParameter
LspSignatureActiveParameter Used to highlight the active parameter in the signature help. Seevim.lsp.handlers.signature_help().

LSP SEMANTIC HIGHLIGHTSlsp-semantic-highlight

When available, the LSP client highlights code usinglsp-semantic_tokens,which are another way that LSP servers can provide information about sourcecode. Note that this is in addition to treesitter syntax highlighting;semantic highlighting does not replace syntax highlighting.
The server will typically provide one token per identifier in the source code.The token will have atype such as "function" or "variable", and 0 or moremodifiers such as "readonly" or "deprecated." The standard types andmodifiers are described here:https://microsoft.github.io/language-server-protocol/specification/#textDocument_semanticTokensLSP servers may also use off-spec types and modifiers.
The LSP client adds one or more highlights for each token. The highlightgroups are derived from the token's type and modifiers:
@lsp.type.<type>.<ft> for the type
@lsp.mod.<mod>.<ft> for each modifier
@lsp.typemod.<type>.<mod>.<ft> for each modifierUse:Inspect to view the highlights for a specific token. Use:hi ornvim_set_hl() to change the appearance of semantic highlights:
hi @lsp.type.function guifg=Yellow        " function names are yellowhi @lsp.type.variable.lua guifg=Green     " variables in lua are greenhi @lsp.mod.deprecated gui=strikethrough  " deprecated is crossed outhi @lsp.typemod.function.async guifg=Blue " async functions are blue
The valuevim.hl.priorities.semantic_tokens is the priority of the@lsp.type.* highlights. The@lsp.mod.* and@lsp.typemod.* highlightshave priorities one and two higher, respectively.
You can disable semantic highlights by clearing the highlight groups:
-- Hide semantic highlights for functionsvim.api.nvim_set_hl(0, '@lsp.type.function', {})-- Hide all semantic highlightsfor _, group in ipairs(vim.fn.getcompletion("@lsp", "highlight")) do  vim.api.nvim_set_hl(0, group, {})end
You probably want these inside aColorScheme autocommand.
UseLspTokenUpdate andvim.lsp.semantic_tokens.highlight_token() for morecomplex highlighting.
The following is a list of standard captures used in queries for Nvim,highlighted according to the current colorscheme (use:Inspect on one to seethe exact definition):
@lsp.type.class Identifiers that declare or reference a class type@lsp.type.comment Tokens that represent a comment@lsp.type.decorator Identifiers that declare or reference decorators and annotations@lsp.type.enum Identifiers that declare or reference an enumeration type@lsp.type.enumMember Identifiers that declare or reference an enumeration property, constant, or member@lsp.type.event Identifiers that declare an event property@lsp.type.function Identifiers that declare a function@lsp.type.interface Identifiers that declare or reference an interface type@lsp.type.keyword Tokens that represent a language keyword@lsp.type.macro Identifiers that declare a macro@lsp.type.method Identifiers that declare a member function or method@lsp.type.modifier Tokens that represent a modifier@lsp.type.namespace Identifiers that declare or reference a namespace, module, or package@lsp.type.number Tokens that represent a number literal@lsp.type.operator Tokens that represent an operator@lsp.type.parameter Identifiers that declare or reference a function or method parameters@lsp.type.property Identifiers that declare or reference a member property, member field, or member variable@lsp.type.regexp Tokens that represent a regular expression literal@lsp.type.string Tokens that represent a string literal@lsp.type.struct Identifiers that declare or reference a struct type@lsp.type.type Identifiers that declare or reference a type that is not covered above@lsp.type.typeParameter Identifiers that declare or reference a type parameter@lsp.type.variable Identifiers that declare or reference a local or global variable
@lsp.mod.abstract Types and member functions that are abstract@lsp.mod.async Functions that are marked async@lsp.mod.declaration Declarations of symbols@lsp.mod.defaultLibrary Symbols that are part of the standard library@lsp.mod.definition Definitions of symbols, for example, in header files@lsp.mod.deprecated Symbols that should no longer be used@lsp.mod.documentation Occurrences of symbols in documentation@lsp.mod.modification Variable references where the variable is assigned to@lsp.mod.readonly Readonly variables and member fields (constants)@lsp.mod.static Class members (static members)

EVENTSlsp-events

LspAttachLspAttach
After an LSP client performs "initialize" and attaches to a buffer. Theautocmd-pattern is the buffer name. The client ID is passed in the Lua handlerevent-data argument.
Example:
vim.api.nvim_create_autocmd('LspAttach', {  callback = function(ev)    local client = vim.lsp.get_client_by_id(ev.data.client_id)    -- ...  end})
Note: If the LSP server performs dynamic registration, capabilities may be registered any time _after_ LspAttach. In that case you may want to handle the "registerCapability" event.
Example:
vim.lsp.handlers['client/registerCapability'] = (function(overridden)  return function(err, res, ctx)    local result = overridden(err, res, ctx)    local client = vim.lsp.get_client_by_id(ctx.client_id)    if not client then      return    end    for bufnr, _ in pairs(client.attached_buffers) do      -- Call your custom on_attach logic...      -- my_on_attach(client, bufnr)    end    return result  endend)(vim.lsp.handlers['client/registerCapability'])
LspDetachLspDetach
Just before an LSP client detaches from a buffer. Theautocmd-pattern is the buffer name. The client ID is passed in the Lua handlerevent-data argument.
Example:
vim.api.nvim_create_autocmd('LspDetach', {  callback = function(args)    -- Get the detaching client    local client = vim.lsp.get_client_by_id(args.data.client_id)    -- Remove the autocommand to format the buffer on save, if it exists    if client:supports_method('textDocument/formatting') then      vim.api.nvim_clear_autocmds({        event = 'BufWritePre',        buffer = args.buf,      })    end  end,})
LspNotifyLspNotify
This event is triggered after each successful notification sent to an LSP server.
The client_id, LSP method, and parameters are sent in the Lua handlerevent-data table argument.
Example:
vim.api.nvim_create_autocmd('LspNotify', {  callback = function(args)    local bufnr = args.buf    local client_id = args.data.client_id    local method = args.data.method    local params = args.data.params    -- do something with the notification    if method == 'textDocument/...' then      update_buffer(bufnr)    end  end,})
LspProgressLspProgress
Upon receipt of a progress notification from the server. Notifications can be polled from aprogress ring buffer of avim.lsp.Client or usevim.lsp.status() to get an aggregate message.
If the server sends a "work done progress", thepattern is set tokind (one ofbegin,report orend).
The Lua handlerevent-data argument hasclient_id andparams properties, whereparams is the request params sent by the server (seelsp.ProgressParams).
Example:
autocmd LspProgress * redrawstatus
LspRequestLspRequest
For each request sent to an LSP server, this event is triggered for every change to the request's status. The status can be one ofpending,complete, orcancel and is sent as the{type} on the "data" table passed to the callback function.
It triggers when the initial request is sent ({type} ==pending) and when the LSP server responds ({type} ==complete). If a cancellation is requested usingclient.cancel_request(request_id), then this event will trigger with{type} ==cancel.
The Lua handlerevent-data argument has the client ID, request ID, and request (described atvim.lsp.Client,{requests} field). If the request type iscomplete, the request will be deleted from the client's pending requests table after processing the event handlers.
Example:
vim.api.nvim_create_autocmd('LspRequest', {  callback = function(args)    local bufnr = args.buf    local client_id = args.data.client_id    local request_id = args.data.request_id    local request = args.data.request    if request.type == 'pending' then      -- do something with pending requests      track_pending(client_id, bufnr, request_id, request)    elseif request.type == 'cancel' then      -- do something with pending cancel requests      track_canceling(client_id, bufnr, request_id, request)    elseif request.type == 'complete' then      -- do something with finished requests. this pending      -- request entry is about to be removed since it is complete      track_finish(client_id, bufnr, request_id, request)    end  end,})
LspTokenUpdateLspTokenUpdate
When a visible semantic token is sent or updated by the LSP server, or when an existing token becomes visible for the first time. Theautocmd-pattern is the buffer name. The Lua handlerevent-data argument has the client ID and token (seevim.lsp.semantic_tokens.get_at_pos()).
Example:
vim.api.nvim_create_autocmd('LspTokenUpdate', {  callback = function(args)    local token = args.data.token    if token.type == 'variable' and not token.modifiers.readonly then      vim.lsp.semantic_tokens.highlight_token(        token, args.buf, args.data.client_id, 'MyMutableVariableHighlight'      )    end  end,})
Note: doing anything other than callingvim.lsp.semantic_tokens.highlight_token() is considered experimental.

Lua module: vim.lsplsp-core

vim.lsp.Config Extends:vim.lsp.ClientConfig
Fields:
{cmd} (string[]|fun(dispatchers: vim.lsp.rpc.Dispatchers): vim.lsp.rpc.PublicClient) Seecmd invim.lsp.ClientConfig.
{filetypes} (string[]) Filetypes the client will attach to, if activated byvim.lsp.enable(). If not provided, the client will attach to all filetypes.
{reuse_client} (fun(client: vim.lsp.Client, config: vim.lsp.ClientConfig): boolean) Predicate which decides if a client should be re-used. Used on all running clients. The default implementation re-uses a client if name and root_dir matches.
{root_dir} (string|fun(bufnr: integer, on_dir:fun(root_dir?:string)))lsp-root_dir() Directory where the LSP server will base its workspaceFolders, rootUri, and rootPath on initialization. The function form receives a buffer number andon_dir callback which it must call to provide root_dir, or LSP will not be activated for the buffer. Thus aroot_dir() function can dynamically decide per-buffer whether to activate (or skip) LSP. See example atvim.lsp.enable().
{root_markers} ((string|string[])[]) Directory markers (.e.g. '.git/') where the LSP server will base its workspaceFolders, rootUri, and rootPath on initialization. Unused ifroot_dir is provided.
The list order decides the priority. To indicate "equal priority", specify names in a nested list ({ { 'a', 'b' }, ... }) Each entry in this list is a set of one or more markers. For each set, Nvim will search upwards for each marker contained in the set. If a marker is found, the directory which contains that marker is used as the root directory. If no markers from the set are found, the process is repeated with the next set in the list.
Example:
root_markers = { 'stylua.toml', '.git' }
Find the first parent directory containing the filestylua.toml. If not found, find the first parent directory containing the file or directory.git.
Example:
root_markers = { { 'stylua.toml', '.luarc.json' }, '.git' }
Find the first parent directory containing EITHERstylua.toml or.luarc.json. If not found, find the first parent directory containing the file or directory.git.
buf_attach_client({bufnr},{client_id})vim.lsp.buf_attach_client()
Implements thetextDocument/did… notifications required to track a buffer for any language server.
Without calling this, the server won't be notified of changes to a buffer.
Parameters:
{bufnr} (integer) Buffer handle, or 0 for current
{client_id} (integer) Client id
Return:
(boolean) successtrue if client was attached successfully;false otherwise
buf_detach_client({bufnr},{client_id})vim.lsp.buf_detach_client()
Detaches client from the specified buffer. Note: While the server is notified that the text document (buffer) was closed, it is still able to send notifications should it ignore this notification.
Parameters:
{bufnr} (integer) Buffer handle, or 0 for current
{client_id} (integer) Client id
buf_is_attached({bufnr},{client_id})vim.lsp.buf_is_attached()
Checks if a buffer is attached for a particular client.
Parameters:
{bufnr} (integer) Buffer handle, or 0 for current
{client_id} (integer) the client id
buf_notify({bufnr},{method},{params})vim.lsp.buf_notify()
Send a notification to a server
Attributes:
Since: 0.5.0
Parameters:
{bufnr} (integer?) The number of the buffer
{method} (string) Name of the request method
{params} (any) Arguments to send to the server
Return:
(boolean) success true if any client returns true; false otherwise
vim.lsp.buf_request_all()
buf_request_all({bufnr},{method},{params},{handler}) Sends an async request for all active clients attached to the buffer and executes thehandler callback with the combined result.
Attributes:
Since: 0.5.0
Parameters:
{bufnr} (integer) Buffer handle, or 0 for current.
{method} (string) LSP method name
{params} (table|(fun(client: vim.lsp.Client, bufnr: integer): table?)?) Parameters to send to the server. Can also be passed as a function that returns the params table for cases where parameters are specific to the client.
{handler} (function) Handler called after all requests are completed. Server results are passed as aclient_id:result map.
Return:
(function) cancel Function that cancels all requests.
vim.lsp.buf_request_sync()
buf_request_sync({bufnr},{method},{params},{timeout_ms}) Sends a request to all server and waits for the response of all of them.
Callsvim.lsp.buf_request_all() but blocks Nvim while awaiting the result. Parameters are the same asvim.lsp.buf_request_all() but the result is different. Waits a maximum of{timeout_ms}.
Attributes:
Since: 0.5.0
Parameters:
{bufnr} (integer) Buffer handle, or 0 for current.
{method} (string) LSP method name
{params} (table|(fun(client: vim.lsp.Client, bufnr: integer): table?)?) Parameters to send to the server. Can also be passed as a function that returns the params table for cases where parameters are specific to the client.
{timeout_ms} (integer?, default:1000) Maximum time in milliseconds to wait for a result.
Return (multiple):
(table<integer, {error: lsp.ResponseError?, result: any}>?) result Map of client_id:request_result. (string?) err On timeout, cancel, or error,err is a string describing the failure reason, andresult is nil.
commandsvim.lsp.commands
Registry (a table) for client-side handlers, for custom server-commands that are not in the LSP specification.
If an LSP response contains a command which is not found invim.lsp.commands, the command will be executed via the LSP server usingworkspace/executeCommand.
Each key in the table is a unique command name, and each value is a function which is called when an LSP action (code action, code lenses, …) triggers the command.
Argument 1 is theCommand:
Commandtitle: Stringcommand: Stringarguments?: any[]
Argument 2 is thelsp-handlerctx.
Example:
vim.lsp.commands['java.action.generateToStringPrompt'] = function(_, ctx)  require("jdtls.async").run(function()    local _, result = request(ctx.bufnr, 'java/checkToStringStatus', ctx.params)    local fields = ui.pick_many(result.fields, 'Include item in toString?', function(x)      return string.format('%s: %s', x.name, x.type)    end)    local _, edit = request(ctx.bufnr, 'java/generateToString', { context = ctx.params; fields = fields; })    vim.lsp.util.apply_workspace_edit(edit, offset_encoding)  end)end
config({name},{cfg})vim.lsp.config()
Sets the default configuration for an LSP client (or all clients if the special name "*" is used).
Can also be accessed by table-indexing (vim.lsp.config[…]) to get the resolved config, or redefine the config (instead of "merging" with the config chain).
Examples:
Add root markers for ALL clients:
vim.lsp.config('*', {  root_markers = { '.git', '.hg' },})
Add capabilities to ALL clients:
  vim.lsp.config('*', {  capabilities = {    textDocument = {      semanticTokens = {        multilineTokenSupport = true,      }    }  }})
Add root markers and capabilities for "clangd":
  vim.lsp.config('clangd', {  root_markers = { '.clang-format', 'compile_commands.json' },  capabilities = {    textDocument = {      completion = {        completionItem = {          snippetSupport = true,        }      }    }  }})
(Re-)define the "clangd" configuration (overrides the resolved chain):
  vim.lsp.config.clangd = {  cmd = {    'clangd',    '--clang-tidy',    '--background-index',    '--offset-encoding=utf-8',  },  root_markers = { '.clangd', 'compile_commands.json' },  filetypes = { 'c', 'cpp' },}
Get the resolved configuration for "luals":
local cfg = vim.lsp.config.luals
Attributes:
Since: 0.11.0
Parameters:
{name} (string)
{cfg} (vim.lsp.Config) Seevim.lsp.Config.
enable({name},{enable})vim.lsp.enable()
Auto-starts LSP when a buffer is opened, based on thelsp-configfiletypes,root_markers, androot_dir fields.
Examples:
vim.lsp.enable('clangd')vim.lsp.enable({'luals', 'pyright'})
Example: To dynamically decide whether LSP is activated, define alsp-root_dir() function which callson_dir() only when you want that config to activate:
vim.lsp.config('lua_ls', {  root_dir = function(bufnr, on_dir)    if not vim.fn.bufname(bufnr):match('%.txt$') then      on_dir(vim.fn.getcwd())    end  end})
Attributes:
Since: 0.11.0
Parameters:
{name} (string|string[]) Name(s) of client(s) to enable.
{enable} (boolean?)true|nil to enable,false to disable.
foldclose({kind},{winid})vim.lsp.foldclose()
Close all{kind} of folds in the the window with{winid}.
To automatically fold imports when opening a file, you can use an autocmd:
vim.api.nvim_create_autocmd('LspNotify', {  callback = function(args)    if args.data.method == 'textDocument/didOpen' then      vim.lsp.foldclose('imports', vim.fn.bufwinid(args.buf))    end  end,})
Attributes:
Since: 0.11.0
Parameters:
{kind} (lsp.FoldingRangeKind) Kind to close, one of "comment", "imports" or "region".
{winid} (integer?) Defaults to the current window.
foldexpr({lnum})vim.lsp.foldexpr()
Provides an interface between the built-in client and afoldexpr function.
To use, set'foldmethod' to "expr" and set the value of'foldexpr':
vim.o.foldmethod = 'expr'vim.o.foldexpr = 'v:lua.vim.lsp.foldexpr()'
Or use it only when supported by checking for the "textDocument/foldingRange" capability in anLspAttach autocommand. Example:
vim.o.foldmethod = 'expr'-- Default to treesitter foldingvim.o.foldexpr = 'v:lua.vim.treesitter.foldexpr()'-- Prefer LSP folding if client supports itvim.api.nvim_create_autocmd('LspAttach', {  callback = function(args)    local client = vim.lsp.get_client_by_id(args.data.client_id)    if client:supports_method('textDocument/foldingRange') then      local win = vim.api.nvim_get_current_win()      vim.wo[win][0].foldexpr = 'v:lua.vim.lsp.foldexpr()'    end  end,})
Parameters:
{lnum} (integer) line number
foldtext()vim.lsp.foldtext()
Provides afoldtext function that shows thecollapsedText retrieved, defaults to the first folded line ifcollapsedText is not provided.
formatexpr({opts})vim.lsp.formatexpr()
Provides an interface between the built-in client and aformatexpr function.
Currently only supports a single client. This can be set viasetlocal formatexpr=v:lua.vim.lsp.formatexpr() or (more typically) inon_attach viavim.bo[bufnr].formatexpr = 'v:lua.vim.lsp.formatexpr(#{timeout_ms:250})'.
Parameters:
{opts} (table?) A table with the following fields:
{timeout_ms} (integer, default: 500ms) The timeout period for the formatting request..
vim.lsp.get_buffers_by_client_id()
get_buffers_by_client_id({client_id}) Returns list of buffers attached to client_id.
Parameters:
{client_id} (integer) client id
Return:
(integer[]) buffers list of buffer ids
get_client_by_id({client_id})vim.lsp.get_client_by_id()
Gets a client by id, or nil if the id is invalid or the client was stopped. The returned client may not yet be fully initialized.
Parameters:
{client_id} (integer) client id
Return:
(vim.lsp.Client?) client rpc object
get_clients({filter})vim.lsp.get_clients()
Get active clients.
Attributes:
Since: 0.10.0
Parameters:
{filter} (table?) Key-value pairs used to filter the returned clients.
{id} (integer) Only return clients with the given id
{bufnr} (integer) Only return clients attached to this buffer
{name} (string) Only return clients with the given name
{method} (string) Only return clients supporting the given method
Return:
(vim.lsp.Client[]) List ofvim.lsp.Client objects
get_log_path()vim.lsp.get_log_path()
Gets the path of the logfile used by the LSP client.
Return:
(string) path to log file
is_enabled({name})vim.lsp.is_enabled()
Checks if the given LSP config is enabled (globally, not per-buffer).
Parameters:
{name} (string) Config name
Return:
(boolean)
omnifunc({findstart},{base})vim.lsp.omnifunc()
Implements'omnifunc' compatible LSP completion.
Parameters:
{findstart} (integer) 0 or 1, decides behavior
{base} (integer) findstart=0, text to match against
Return:
(integer|table) Decided by{findstart}:
findstart=0: column where the completion starts, or -2 or -3
findstart=1: list of matches (actually just callscomplete())
See also:
complete-functions
complete-items
CompleteDone
set_log_level({level})vim.lsp.set_log_level()
Sets the global log level for LSP logging.
Levels by name: "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"
Level numbers begin with "TRACE" at 0
Uselsp.log_levels for reverse lookup.
Parameters:
{level} (integer|string) the case insensitive level name or number
See also:
vim.lsp.log_levels
start({config},{opts})vim.lsp.start()
Create a new LSP client and start a language server or reuses an already running client if one is found matchingname androot_dir. Attaches the current buffer to the client.
Example:
vim.lsp.start({   name = 'my-server-name',   cmd = {'name-of-language-server-executable'},   root_dir = vim.fs.root(0, {'pyproject.toml', 'setup.py'}),})
Seevim.lsp.ClientConfig for all available options. The most important are:
name arbitrary name for the LSP client. Should be unique per language server.
cmd command string[] or function.
root_dir path to the project root. By default this is used to decide if an existing client should be re-used. The example above usesvim.fs.root() to detect the root by traversing the file system upwards starting from the current directory until either apyproject.toml orsetup.py file is found.
workspace_folders list of{ uri:string, name: string } tables specifying the project root folders used by the language server. Ifnil the property is derived fromroot_dir for convenience.
Language servers use this information to discover metadata like the dependencies of your project and they tend to index the contents within the project folder.
To ensure a language server is only started for languages it can handle, make sure to callvim.lsp.start() within aFileType autocmd. Either use:au,nvim_create_autocmd() or put the call in aftplugin/<filetype_name>.lua (Seeftplugin-name)
Attributes:
Since: 0.8.0
Parameters:
{config} (vim.lsp.ClientConfig) Configuration for the server. Seevim.lsp.ClientConfig.
{opts} (table?) Optional keyword arguments.
{reuse_client} (fun(client: vim.lsp.Client, config: vim.lsp.ClientConfig): boolean) Predicate used to decide if a client should be re-used. Used on all running clients. The default implementation re-uses a client if it has the same name and if the given workspace folders (or root_dir) are all included in the client's workspace folders.
{bufnr} (integer) Buffer handle to attach to if starting or re-using a client (0 for current).
{attach} (boolean) Whether to attach the client to a buffer (default true). If set tofalse,reuse_client andbufnr will be ignored.
{silent} (boolean) Suppress error reporting if the LSP server fails to start (default false).
Return:
(integer?) client_id
status()vim.lsp.status()
Consumes the latest progress messages from all clients and formats them as a string. Empty if there are no clients or if no new messages
Return:
(string)
stop_client({client_id},{force})vim.lsp.stop_client()
Stops a client(s).
You can also use thestop() function on avim.lsp.Client object. To stop all clients:
vim.lsp.stop_client(vim.lsp.get_clients())
By default asks the server to shutdown, unless stop was requested already for this client, then force-shutdown is attempted.
Parameters:
{client_id} (integer|integer[]|vim.lsp.Client[]) id, list of id's, or list ofvim.lsp.Client objects
{force} (boolean?) shutdown forcefully
tagfunc({pattern},{flags})vim.lsp.tagfunc()
Provides an interface between the built-in client and'tagfunc'.
When used with normal mode commands (e.g.CTRL-]) this will invoke the "textDocument/definition" LSP method to find the tag under the cursor. Otherwise, uses "workspace/symbol". If no results are returned from any LSP servers, falls back to using built-in tags.
Parameters:
{pattern} (string) Pattern used to find a workspace symbol
{flags} (string) Seetag-function
Return:
(table[]) tags A list of matching tags

Lua module: vim.lsp.clientlsp-client

vim.lsp.Client
Fields:
{attached_buffers} (table<integer,true>)
{capabilities} (lsp.ClientCapabilities) Capabilities provided by the client (editor or tool), at startup.
{commands} (table<string,fun(command: lsp.Command, ctx: table)>) Client commands. Seevim.lsp.ClientConfig.
{config} (vim.lsp.ClientConfig) Copy of the config passed tovim.lsp.start(). Seevim.lsp.ClientConfig.
{dynamic_capabilities} (lsp.DynamicCapabilities) Capabilities provided at runtime (after startup).
{flags} (table) A table with flags for the client. The current (experimental) flags are:
{allow_incremental_sync} (boolean, default:true) Allow using incremental sync for buffer edits
{debounce_text_changes} (integer, default:150) DebouncedidChange notifications to the server by the given number in milliseconds. No debounce occurs ifnil.
{exit_timeout} (integer|false, default:false) Milliseconds to wait for server to exit cleanly after sending the "shutdown" request before sending kill -15. If set to false, nvim exits immediately after sending the "shutdown" request to the server.
{get_language_id} (fun(bufnr: integer, filetype: string): string) Seevim.lsp.ClientConfig.
{handlers} (table<string,lsp.Handler>) Seevim.lsp.ClientConfig.
{id} (integer) The id allocated to the client.
{initialized} (true?)
{name} (string) Seevim.lsp.ClientConfig.
{offset_encoding} (string) Seevim.lsp.ClientConfig.
{progress} (vim.lsp.Client.Progress) A ring buffer (vim.ringbuf()) containing progress messages sent by the server. Seevim.lsp.Client.Progress.
{requests} (table<integer,{ type: string, bufnr: integer, method: string}?>) The current pending requests in flight to the server. Entries are key-value pairs with the key being the request id while the value is a table withtype,bufnr, andmethod key-value pairs.type is either "pending" for an active request, or "cancel" for a cancel request. It will be "complete" ephemerally while executingLspRequest autocmds when replies are received from the server.
{root_dir} (string?) Seevim.lsp.ClientConfig.
{rpc} (vim.lsp.rpc.PublicClient) RPC client object, for low level interaction with the client. Seevim.lsp.rpc.start().
{server_capabilities} (lsp.ServerCapabilities?) Response from the server sent oninitialize describing the server's capabilities.
{server_info} (lsp.ServerInfo?) Response from the server sent oninitialize describing server information (e.g. version).
{settings} (lsp.LSPObject) Seevim.lsp.ClientConfig.
{workspace_folders} (lsp.WorkspaceFolder[]?) Seevim.lsp.ClientConfig.
{request} (fun(self: vim.lsp.Client, method: string, params: table?, handler: lsp.Handler?, bufnr: integer?): boolean, integer?) SeeClient:request().
{request_sync} (fun(self: vim.lsp.Client, method: string, params: table, timeout_ms: integer?, bufnr: integer?): {err: lsp.ResponseError?, result:any}?, string?) SeeClient:request_sync().
{notify} (fun(self: vim.lsp.Client, method: string, params: table?): boolean) SeeClient:notify().
{cancel_request} (fun(self: vim.lsp.Client, id: integer): boolean) SeeClient:cancel_request().
{stop} (fun(self: vim.lsp.Client, force: boolean?)) SeeClient:stop().
{is_stopped} (fun(self: vim.lsp.Client): boolean) SeeClient:is_stopped().
{exec_cmd} (fun(self: vim.lsp.Client, command: lsp.Command, context: {bufnr?: integer}?, handler: lsp.Handler?)) SeeClient:exec_cmd().
{on_attach} (fun(self: vim.lsp.Client, bufnr: integer)) SeeClient:on_attach().
{supports_method} (fun(self: vim.lsp.Client, method: string, bufnr: integer?)) SeeClient:supports_method().
vim.lsp.Client.Progress Extends:vim.Ringbuf
Fields:
{pending} (table<lsp.ProgressToken,lsp.LSPAny>)
vim.lsp.ClientConfig
Fields:
{before_init} (fun(params: lsp.InitializeParams, config: vim.lsp.ClientConfig)) Callback invoked before the LSP "initialize" phase, whereparams contains the parameters being sent to the server andconfig is the config that was passed tovim.lsp.start(). You can use this to modify parameters before they are sent.
{capabilities} (lsp.ClientCapabilities) Map overriding the default capabilities defined byvim.lsp.protocol.make_client_capabilities(), passed to the language server on initialization. Hint: use make_client_capabilities() and modify its result.
Note: To send an empty dictionary usevim.empty_dict(), else it will be encoded as an array.
{cmd} (string[]|fun(dispatchers: vim.lsp.rpc.Dispatchers): vim.lsp.rpc.PublicClient) command string[] that launches the language server (treated as injobstart(), must be absolute or on$PATH, shell constructs like "~" are not expanded), or function that creates an RPC client. Function receives adispatchers table and returns a table with member functionsrequest,notify,is_closing andterminate. Seevim.lsp.rpc.request(),vim.lsp.rpc.notify(). For TCP there is a builtin RPC client factory:vim.lsp.rpc.connect()
{cmd_cwd} (string, default: cwd) Directory to launch thecmd process. Not related toroot_dir.
{cmd_env} (table) Environment variables passed to the LSP process on spawn. Non-string values are coerced to string. Example:
{ PORT = 8080; HOST = '0.0.0.0'; }
{commands} (table<string,fun(command: lsp.Command, ctx: table)>) Client commands. Map of command names to user-defined functions. Commands passed tostart() take precedence over the global command registry. Each key must be a unique command name, and the value is a function which is called if any LSP action (code action, code lenses, …) triggers the command.
{detached} (boolean, default: true) Daemonize the server process so that it runs in a separate process group from Nvim. Nvim will shutdown the process on exit, but if Nvim fails to exit cleanly this could leave behind orphaned server processes.
{flags} (table) A table with flags for the client. The current (experimental) flags are:
{allow_incremental_sync} (boolean, default:true) Allow using incremental sync for buffer edits
{debounce_text_changes} (integer, default:150) DebouncedidChange notifications to the server by the given number in milliseconds. No debounce occurs ifnil.
{exit_timeout} (integer|false, default:false) Milliseconds to wait for server to exit cleanly after sending the "shutdown" request before sending kill -15. If set to false, nvim exits immediately after sending the "shutdown" request to the server.
{get_language_id} (fun(bufnr: integer, filetype: string): string) Language ID as string. Defaults to the buffer filetype.
{handlers} (table<string,function>) Map of LSP method names tolsp-handlers.
{init_options} (lsp.LSPObject) Values to pass in the initialization request asinitializationOptions. Seeinitialize in the LSP spec.
{name} (string) (default: client-id) Name in logs and user messages.
{offset_encoding} ('utf-8'|'utf-16'|'utf-32') Called "position encoding" in LSP spec. The encoding that the LSP server expects, used for communication. Not validated. Can be modified inon_init before text is sent to the server.
{on_attach} (elem_or_list<fun(client: vim.lsp.Client, bufnr: integer)>) Callback invoked when client attaches to a buffer.
{on_error} (fun(code: integer, err: string)) Callback invoked when the client operation throws an error.code is a number describing the error. Other arguments may be passed depending on the error kind. Seevim.lsp.rpc.client_errors for possible errors. Usevim.lsp.rpc.client_errors[code] to get human-friendly name.
{on_exit} (elem_or_list<fun(code: integer, signal: integer, client_id: integer)>) Callback invoked on client exit.
code: exit code of the process
signal: number describing the signal used to terminate (if any)
client_id: client handle
{on_init} (elem_or_list<fun(client: vim.lsp.Client, init_result: lsp.InitializeResult)>) Callback invoked after LSP "initialize", whereresult is a table ofcapabilities and anything else the server may send. For example, clangd sendsinit_result.offsetEncoding ifcapabilities.offsetEncoding was sent to it. You can only modify theclient.offset_encoding here before any notifications are sent.
{root_dir} (string) Directory where the LSP server will base its workspaceFolders, rootUri, and rootPath on initialization.
{settings} (lsp.LSPObject) Map of language server-specific settings, decided by the client. Sent to the LS if requested viaworkspace/configuration. Keys are case-sensitive.
{trace} ('off'|'messages'|'verbose', default: "off") Passed directly to the language server in the initialize request. Invalid/empty values will
{workspace_folders} (lsp.WorkspaceFolder[]) List of workspace folders passed to the language server. For backwards compatibility rootUri and rootPath are derived from the first workspace folder in this list. Can benull if the client supports workspace folders but none are configured. SeeworkspaceFolders in LSP spec.
{workspace_required} (boolean) (default false) Server requires a workspace (no "single file" support). Note: Without a workspace, cross-file features (navigation, hover) may or may not work depending on the language server, even if the server doesn't require a workspace.
Client:cancel_request({id})Client:cancel_request()
Cancels a request with a given request id.
Parameters:
{id} (integer) id of request to cancel
Return:
(boolean) status indicating if the notification was successful.
See also:
Client:notify()
Client:exec_cmd({command},{context},{handler})Client:exec_cmd()
Execute a lsp command, either via client command function (if available) or via workspace/executeCommand (if supported by the server)
Parameters:
{command} (lsp.Command)
{context} ({bufnr?: integer}?)
{handler} (lsp.Handler?) only called if a server command
Client:is_stopped()Client:is_stopped()
Checks whether a client is stopped.
Return:
(boolean) true if client is stopped or in the process of being stopped; false otherwise
Client:notify({method},{params})Client:notify()
Sends a notification to an LSP server.
Parameters:
{method} (string) LSP method name.
{params} (table?) LSP request params.
Return:
(boolean) status indicating if the notification was successful. If it is false, then the client has shutdown.
Client:on_attach({bufnr})Client:on_attach()
Runs the on_attach function from the client's config if it was defined. Useful for buffer-local setup.
Parameters:
{bufnr} (integer) Buffer number
Client:request()
Client:request({method},{params},{handler},{bufnr}) Sends a request to the server.
This is a thin wrapper around{client.rpc.request} with some additional checks for capabilities and handler availability.
Parameters:
{method} (string) LSP method name.
{params} (table?) LSP request params.
{handler} (lsp.Handler?) Responselsp-handler for this method.
{bufnr} (integer?) (default: 0) Buffer handle, or 0 for current.
Return (multiple):
(boolean) status indicates whether the request was successful. If it isfalse, then it will always befalse (the client has shutdown). (integer?) request_id Can be used withClient:cancel_request().nil is request failed.
See also:
vim.lsp.buf_request_all()
Client:request_sync()
Client:request_sync({method},{params},{timeout_ms},{bufnr}) Sends a request to the server and synchronously waits for the response.
This is a wrapper aroundClient:request()
Parameters:
{method} (string) LSP method name.
{params} (table) LSP request params.
{timeout_ms} (integer?) Maximum time in milliseconds to wait for a result. Defaults to 1000
{bufnr} (integer?) (default: 0) Buffer handle, or 0 for current.
Return (multiple):
({err: lsp.ResponseError?, result:any}?)result anderr from thelsp-handler.nil is the request was unsuccessful (string?) err On timeout, cancel or error, whereerr is a string describing the failure reason.
See also:
vim.lsp.buf_request_sync()
Client:stop({force})Client:stop()
Stops a client, optionally with force.
By default, it will just request the server to shutdown without force. If you request to stop a client which has previously been requested to shutdown, it will automatically escalate and force shutdown.
Parameters:
{force} (boolean?)
Client:supports_method({method},{bufnr})Client:supports_method()
Checks if a client supports a given method. Always returns true for unknown off-spec methods.
Note: Some language server capabilities can be file specific.
Parameters:
{method} (string)
{bufnr} (integer?)

Lua module: vim.lsp.buflsp-buf

Thevim.lsp.buf_… functions perform operations for LSP clients attached tothe current buffer.
vim.lsp.ListOpts
Fields:
{on_list} (fun(t: vim.lsp.LocationOpts.OnList)) list-handler replacing the default handler. Called for any non-empty result. This table can be used withsetqflist() orsetloclist(). E.g.:
local function on_list(options)  vim.fn.setqflist({}, ' ', options)  vim.cmd.cfirst()endvim.lsp.buf.definition({ on_list = on_list })vim.lsp.buf.references(nil, { on_list = on_list })
{loclist} (boolean) Whether to use thelocation-list or thequickfix list in the default handler.
vim.lsp.buf.definition({ loclist = true })vim.lsp.buf.references(nil, { loclist = false })
vim.lsp.LocationOpts Extends:vim.lsp.ListOpts
Fields:
{reuse_win} (boolean) Jump to existing window if buffer is already open.
vim.lsp.LocationOpts.OnList
Fields:
{items} (table[]) Structured likesetqflist-what
{title} (string) Title for the list.
{context} ({ bufnr: integer, method: string }) Subset ofctx fromlsp-handler.
vim.lsp.buf.hover.Opts Extends:vim.lsp.util.open_floating_preview.Opts
Fields:
{silent} (boolean)
vim.lsp.buf.signature_help.Opts Extends:vim.lsp.util.open_floating_preview.Opts
Fields:
{silent} (boolean)
vim.lsp.buf.add_workspace_folder()
add_workspace_folder({workspace_folder}) Add the folder at path to the workspace folders. If{path} is not provided, the user will be prompted for a path usinginput().
Parameters:
{workspace_folder} (string?)
clear_references()vim.lsp.buf.clear_references()
Removes document highlights from current buffer.
code_action({opts})vim.lsp.buf.code_action()
Selects a code action (LSP: "textDocument/codeAction" request) available at cursor position.
Parameters:
{opts} (table?) A table with the following fields:
{context} (lsp.CodeActionContext) Corresponds toCodeActionContext of the LSP specification:
{diagnostics} (table) LSPDiagnostic[]. Inferred from the current position if not provided.
{only} (table) List of LSPCodeActionKinds used to filter the code actions. Most language servers support values likerefactor orquickfix.
{triggerKind} (integer) The reason why code actions were requested.
{filter} (fun(x: lsp.CodeAction|lsp.Command):boolean) Predicate taking anCodeAction and returning a boolean.
{apply} (boolean) When set totrue, and there is just one remaining action (after filtering), the action is applied without user query.
{range} ({start: integer[], end: integer[]}) Range for which code actions should be requested. If in visual mode this defaults to the active selection. Table must containstart andend keys with{row,col} tuples using mark-like indexing. Seeapi-indexing
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_codeAction
vim.lsp.protocol.CodeActionTriggerKind
declaration({opts})vim.lsp.buf.declaration()
Jumps to the declaration of the symbol under the cursor.
Note:
Many servers do not implement this method. Generally, seevim.lsp.buf.definition() instead.
Parameters:
{opts} (vim.lsp.LocationOpts?) Seevim.lsp.LocationOpts.
definition({opts})vim.lsp.buf.definition()
Jumps to the definition of the symbol under the cursor.
Parameters:
{opts} (vim.lsp.LocationOpts?) Seevim.lsp.LocationOpts.
document_highlight()vim.lsp.buf.document_highlight()
Send request to the server to resolve document highlights for the current text document position. This request can be triggered by a key mapping or by events such asCursorHold, e.g.:
autocmd CursorHold  <buffer> lua vim.lsp.buf.document_highlight()autocmd CursorHoldI <buffer> lua vim.lsp.buf.document_highlight()autocmd CursorMoved <buffer> lua vim.lsp.buf.clear_references()
Note: Usage ofvim.lsp.buf.document_highlight() requires the following highlight groups to be defined or you won't be able to see the actual highlights.hl-LspReferenceTexthl-LspReferenceReadhl-LspReferenceWrite
document_symbol({opts})vim.lsp.buf.document_symbol()
Lists all symbols in the current buffer in thelocation-list.
Parameters:
{opts} (vim.lsp.ListOpts?) Seevim.lsp.ListOpts.
format({opts})vim.lsp.buf.format()
Formats a buffer using the attached (and optionally filtered) language server clients.
Parameters:
{opts} (table?) A table with the following fields:
{formatting_options} (table) Can be used to specify FormattingOptions. Some unspecified options will be automatically derived from the current Nvim options. Seehttps://microsoft.github.io/language-server-protocol/specification/#formattingOptions
{timeout_ms} (integer, default:1000) Time in milliseconds to block for formatting requests. No effect if async=true.
{bufnr} (integer, default: current buffer) Restrict formatting to the clients attached to the given buffer.
{filter} (fun(client: vim.lsp.Client): boolean?) Predicate used to filter clients. Receives a client as argument and must return a boolean. Clients matching the predicate are included. Example:
-- Never request typescript-language-server for formattingvim.lsp.buf.format {  filter = function(client) return client.name ~= "ts_ls" end}
{async} (boolean, default: false) If true the method won't block. Editing the buffer while formatting asynchronous can lead to unexpected changes.
{id} (integer) Restrict formatting to the client with ID (client.id) matching this field.
{name} (string) Restrict formatting to the client with name (client.name) matching this field.
{range} ({start:[integer,integer],end:[integer, integer]}|{start:[integer,integer],end:[integer,integer]}[], default: current selection in visual mode,nil in other modes, formatting the full buffer) Range to format. Table must containstart andend keys with{row,col} tuples using (1,0) indexing. Can also be a list of tables that containstart andend keys as described above, in which casetextDocument/rangesFormatting support is required.
hover({config})vim.lsp.buf.hover()
Displays hover information about the symbol under the cursor in a floating window. The window will be dismissed on cursor move. Calling the function twice will jump into the floating window (thus by default, "KK" will open the hover window and focus it). In the floating window, all commands and mappings are available as usual, except that "q" dismisses the window. You can scroll the contents the same as you would any other buffer.
Note: to disable hover highlights, add the following to your config:
vim.api.nvim_create_autocmd('ColorScheme', {  callback = function()    vim.api.nvim_set_hl(0, 'LspReferenceTarget', {})  end,})
Parameters:
{config} (vim.lsp.buf.hover.Opts?) Seevim.lsp.buf.hover.Opts.
implementation({opts})vim.lsp.buf.implementation()
Lists all the implementations for the symbol under the cursor in the quickfix window.
Parameters:
{opts} (vim.lsp.LocationOpts?) Seevim.lsp.LocationOpts.
incoming_calls()vim.lsp.buf.incoming_calls()
Lists all the call sites of the symbol under the cursor in thequickfix window. If the symbol can resolve to multiple items, the user can pick one in theinputlist().
list_workspace_folders()vim.lsp.buf.list_workspace_folders()
List workspace folders.
outgoing_calls()vim.lsp.buf.outgoing_calls()
Lists all the items that are called by the symbol under the cursor in thequickfix window. If the symbol can resolve to multiple items, the user can pick one in theinputlist().
references({context},{opts})vim.lsp.buf.references()
Lists all the references to the symbol under the cursor in the quickfix window.
Parameters:
{context} (lsp.ReferenceContext?) Context for the request
{opts} (vim.lsp.ListOpts?) Seevim.lsp.ListOpts.
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_references
vim.lsp.buf.remove_workspace_folder()
remove_workspace_folder({workspace_folder}) Remove the folder at path from the workspace folders. If{path} is not provided, the user will be prompted for a path usinginput().
Parameters:
{workspace_folder} (string?)
rename({new_name},{opts})vim.lsp.buf.rename()
Renames all references to the symbol under the cursor.
Parameters:
{new_name} (string?) If not provided, the user will be prompted for a new name usingvim.ui.input().
{opts} (table?) Additional options:
{filter} (fun(client: vim.lsp.Client): boolean?) Predicate used to filter clients. Receives a client as argument and must return a boolean. Clients matching the predicate are included.
{name} (string) Restrict clients used for rename to ones where client.name matches this field.
{bufnr} (integer) (default: current buffer)
signature_help({config})vim.lsp.buf.signature_help()
Displays signature information about the symbol under the cursor in a floating window.
Parameters:
{config} (vim.lsp.buf.signature_help.Opts?) Seevim.lsp.buf.signature_help.Opts.
type_definition({opts})vim.lsp.buf.type_definition()
Jumps to the definition of the type of the symbol under the cursor.
Parameters:
{opts} (vim.lsp.LocationOpts?) Seevim.lsp.LocationOpts.
typehierarchy({kind})vim.lsp.buf.typehierarchy()
Lists all the subtypes or supertypes of the symbol under the cursor in thequickfix window. If the symbol can resolve to multiple items, the user can pick one usingvim.ui.select().
Parameters:
{kind} ("subtypes"|"supertypes")
workspace_symbol({query},{opts})vim.lsp.buf.workspace_symbol()
Lists all symbols in the current workspace in the quickfix window.
The list is filtered against{query}; if the argument is omitted from the call, the user is prompted to enter a string on the command line. An empty string means no filtering is done.
Parameters:
{query} (string?) optional
{opts} (vim.lsp.ListOpts?) Seevim.lsp.ListOpts.

Lua module: vim.lsp.diagnosticlsp-diagnostic

from({diagnostics})vim.lsp.diagnostic.from()
Converts the inputvim.Diagnostics to LSP diagnostics.
Parameters:
{diagnostics} (vim.Diagnostic[])
Return:
(lsp.Diagnostic[])
vim.lsp.diagnostic.get_namespace()
get_namespace({client_id},{is_pull}) Get the diagnostic namespace associated with an LSP clientvim.diagnostic for diagnostics
Parameters:
{client_id} (integer) The id of the LSP client
{is_pull} (boolean?) Whether the namespace is for a pull or push client. Defaults to push
vim.lsp.diagnostic.on_diagnostic()
on_diagnostic({error},{result},{ctx})lsp-handler for the method "textDocument/diagnostic"
Seevim.diagnostic.config() for configuration options.
Parameters:
{error} (lsp.ResponseError?)
{result} (lsp.DocumentDiagnosticReport)
{ctx} (lsp.HandlerContext)
vim.lsp.diagnostic.on_publish_diagnostics()
on_publish_diagnostics({_},{params},{ctx})lsp-handler for the method "textDocument/publishDiagnostics"
Seevim.diagnostic.config() for configuration options.
Parameters:
{params} (lsp.PublishDiagnosticsParams)
{ctx} (lsp.HandlerContext)

Lua module: vim.lsp.codelenslsp-codelens

clear({client_id},{bufnr})vim.lsp.codelens.clear()
Clear the lenses
Parameters:
{client_id} (integer?) filter by client_id. All clients if nil
{bufnr} (integer?) filter by buffer. All buffers if nil, 0 for current buffer
display({lenses},{bufnr},{client_id})vim.lsp.codelens.display()
Display the lenses using virtual text
Parameters:
{lenses} (lsp.CodeLens[]?) lenses to display
{bufnr} (integer)
{client_id} (integer)
get({bufnr})vim.lsp.codelens.get()
Return all lenses for the given buffer
Parameters:
{bufnr} (integer) Buffer number. 0 can be used for the current buffer.
Return:
(lsp.CodeLens[])
on_codelens({err},{result},{ctx})vim.lsp.codelens.on_codelens()
lsp-handler for the methodtextDocument/codeLens
Parameters:
{err} (lsp.ResponseError?)
{result} (lsp.CodeLens[])
{ctx} (lsp.HandlerContext)
refresh({opts})vim.lsp.codelens.refresh()
Refresh the lenses.
It is recommended to trigger this using an autocmd or via keymap.
Example:
autocmd BufEnter,CursorHold,InsertLeave <buffer> lua vim.lsp.codelens.refresh({ bufnr = 0 })
Parameters:
{opts} (table?) Optional fields
{bufnr} (integer?) filter by buffer. All buffers if nil, 0 for current buffer
run()vim.lsp.codelens.run()
Run the code lens in the current line
save({lenses},{bufnr},{client_id})vim.lsp.codelens.save()
Store lenses for a specific buffer and client
Parameters:
{lenses} (lsp.CodeLens[]?) lenses to store
{bufnr} (integer)
{client_id} (integer)

Lua module: vim.lsp.completionlsp-completion

Thevim.lsp.completion module enables insert-mode completion driven by anLSP server. Callenable() to make it available through Nvim builtincompletion (via theCompleteDone event). Specifyautotrigger=true toactivate "auto-completion" when you type any of the server-definedtriggerCharacters. UseCTRL-Y to select an item from the completion menu.complete_CTRL-Y
Example: activate LSP-driven auto-completion:
-- Works best with completeopt=noselect.-- Use CTRL-Y to select an item. |complete_CTRL-Y|vim.cmd[[set completeopt+=menuone,noselect,popup]]vim.lsp.start({  name = 'ts_ls',  cmd = …,  on_attach = function(client, bufnr)    vim.lsp.completion.enable(true, client.id, bufnr, {      autotrigger = true,      convert = function(item)        return { abbr = item.label:gsub('%b()', '') }      end,    })  end,})
lsp-autocompletion
The LSPtriggerCharacters field decides when to trigger autocompletion. Ifyou want to trigger on EVERY keypress you can either:
Extendclient.server_capabilities.completionProvider.triggerCharacters onLspAttach, before you callvim.lsp.completion.enable(… {autotrigger=true}). See thelsp-attach example.
Callvim.lsp.completion.get() from the handler described atcompl-autocomplete.
vim.lsp.completion.enable()
enable({enable},{client_id},{bufnr},{opts}) Enables or disables completions from the given language client in the given buffer. Effects of enabling completions are:
Callingvim.lsp.completion.get() uses the enabled clients to retrieve completion candidates
Accepting a completion candidate using<c-y> applies side effects like expanding snippets, text edits (e.g. insert import statements) and executing associated commands. This works for completions triggered via autotrigger, omnifunc or completion.get()
Example:lsp-attachlsp-completion
Note: the behavior ofautotrigger=true is controlled by the LSPtriggerCharacters field. You can override it on LspAttach, seelsp-autocompletion.
Parameters:
{enable} (boolean) True to enable, false to disable
{client_id} (integer) Client ID
{bufnr} (integer) Buffer handle, or 0 for the current buffer
{opts} (table?) A table with the following fields:
{autotrigger} (boolean) (default: false) When true, completion triggers automatically based on the server'striggerCharacters.
{convert} (fun(item: lsp.CompletionItem): table) Transforms an LSP CompletionItem tocomplete-items.
get({opts})vim.lsp.completion.get()
Triggers LSP completion once in the current buffer, if LSP completion is enabled (seelsp-attachlsp-completion).
Used by the default LSPomnicompletion providervim.lsp.omnifunc(), thusi_CTRL-X_CTRL-O invokes this in LSP-enabled buffers. UseCTRL-Y to select an item from the completion menu.complete_CTRL-Y
To invoke manually withCTRL-space, use this mapping:
-- Use CTRL-space to trigger LSP completion.-- Use CTRL-Y to select an item. |complete_CTRL-Y|vim.keymap.set('i', '<c-space>', function()  vim.lsp.completion.get()end)
Parameters:
{opts} (table?) A table with the following fields:
{ctx} (lsp.CompletionContext) Completion context. Defaults to a trigger kind ofinvoked.

Lua module: vim.lsp.inlay_hintlsp-inlay_hint

enable({enable},{filter})vim.lsp.inlay_hint.enable()
Enables or disables inlay hints for the{filter}ed scope.
To "toggle", pass the inverse ofis_enabled():
vim.lsp.inlay_hint.enable(not vim.lsp.inlay_hint.is_enabled())
Attributes:
Since: 0.10.0
Parameters:
{enable} (boolean?) true/nil to enable, false to disable
{filter} (table?) Optional filterskwargs, ornil for all.
{bufnr} (integer?) Buffer number, or 0 for current buffer, or nil for all.
get({filter})vim.lsp.inlay_hint.get()
Get the list of inlay hints, (optionally) restricted by buffer or range.
Example usage:
local hint = vim.lsp.inlay_hint.get({ bufnr = 0 })[1] -- 0 for current bufferlocal client = vim.lsp.get_client_by_id(hint.client_id)local resp = client:request_sync('inlayHint/resolve', hint.inlay_hint, 100, 0)local resolved_hint = assert(resp and resp.result, resp.err)vim.lsp.util.apply_text_edits(resolved_hint.textEdits, 0, client.encoding)location = resolved_hint.label[1].locationclient:request('textDocument/hover', {  textDocument = { uri = location.uri },  position = location.range.start,})
Attributes:
Since: 0.10.0
Parameters:
{filter} (table?) Optional filterskwargs:
{bufnr} (integer?)
{range} (lsp.Range?)
Return:
(table[]) A list of objects with the following fields:
{bufnr} (integer)
{client_id} (integer)
{inlay_hint} (lsp.InlayHint)
is_enabled({filter})vim.lsp.inlay_hint.is_enabled()
Query whether inlay hint is enabled in the{filter}ed scope
Attributes:
Since: 0.10.0
Parameters:
{filter} (table?) Optional filterskwargs, ornil for all.
{bufnr} (integer?) Buffer number, or 0 for current buffer, or nil for all.
Return:
(boolean)

Lua module: vim.lsp.semantic_tokenslsp-semantic_tokens

force_refresh({bufnr})vim.lsp.semantic_tokens.force_refresh()
Force a refresh of all semantic tokens
Only has an effect if the buffer is currently active for semantic token highlighting (vim.lsp.semantic_tokens.start() has been called for it)
Parameters:
{bufnr} (integer?) filter by buffer. All buffers if nil, current buffer if 0
vim.lsp.semantic_tokens.get_at_pos()
get_at_pos({bufnr},{row},{col}) Return the semantic token(s) at the given position. If called without arguments, returns the token under the cursor.
Parameters:
{bufnr} (integer?) Buffer number (0 for current buffer, default)
{row} (integer?) Position row (default cursor position)
{col} (integer?) Position column (default cursor position)
Return:
(table?) List of tokens at position. Each token has the following fields:
line (integer) line number, 0-based
start_col (integer) start column, 0-based
end_col (integer) end column, 0-based
type (string) token type as string, e.g. "variable"
modifiers (table) token modifiers as a set. E.g., { static = true, readonly = true }
client_id (integer)
vim.lsp.semantic_tokens.highlight_token()
highlight_token({token},{bufnr},{client_id},{hl_group},{opts}) Highlight a semantic token.
Apply an extmark with a given highlight group for a semantic token. The mark will be deleted by the semantic token engine when appropriate; for example, when the LSP sends updated tokens. This function is intended for use insideLspTokenUpdate callbacks.
Parameters:
{token} (table) A semantic token, found asargs.data.token inLspTokenUpdate
{bufnr} (integer) The buffer to highlight, or0 for current buffer
{client_id} (integer) The ID of thevim.lsp.Client
{hl_group} (string) Highlight group name
{opts} (table?) Optional parameters:
{priority} (integer, default:vim.hl.priorities.semantic_tokens + 3) Priority for the applied extmark.
start({bufnr},{client_id},{opts})vim.lsp.semantic_tokens.start()
Start the semantic token highlighting engine for the given buffer with the given client. The client must already be attached to the buffer.
NOTE: This is currently called automatically byvim.lsp.buf_attach_client(). To opt-out of semantic highlighting with a server that supports it, you can delete the semanticTokensProvider table from the{server_capabilities} of your client in yourLspAttach callback or your configuration'son_attach callback:
client.server_capabilities.semanticTokensProvider = nil
Parameters:
{bufnr} (integer) Buffer number, or0 for current buffer
{client_id} (integer) The ID of thevim.lsp.Client
{opts} (table?) Optional keyword arguments
debounce (integer, default: 200): Debounce token requests to the server by the given number in milliseconds
stop({bufnr},{client_id})vim.lsp.semantic_tokens.stop()
Stop the semantic token highlighting engine for the given buffer with the given client.
NOTE: This is automatically called by aLspDetach autocmd that is set up as part ofstart(), so you should only need this function to manually disengage the semantic token engine without fully detaching the LSP client from the buffer.
Parameters:
{bufnr} (integer) Buffer number, or0 for current buffer
{client_id} (integer) The ID of thevim.lsp.Client

Lua module: vim.lsp.document_colorlsp-document_color

enable({enable},{bufnr},{opts})vim.lsp.document_color.enable()
Enables document highlighting from the given language client in the given buffer.
You can enable document highlighting when a client attaches to a buffer as follows:
vim.api.nvim_create_autocmd('LspAttach', {  callback = function(args)    vim.lsp.document_color.enable(true, args.buf)  end})
To "toggle", pass the inverse ofis_enabled():
vim.lsp.document_color.enable(not vim.lsp.document_color.is_enabled())
Parameters:
{enable} (boolean?) True to enable, false to disable. (default:true)
{bufnr} (integer?) Buffer handle, or 0 for current. (default: 0)
{opts} (table?) A table with the following fields:
{style} ('background'|'foreground'|'virtual'|string|fun(bufnr: integer, range: Range4, hex_code: string)) Highlight style. It can be one of the pre-defined styles, a string to be used as virtual text, or a function that receives the buffer handle, the range (start line, start col, end line, end col) and the resolved hex color. (default:'background')
is_enabled({bufnr})vim.lsp.document_color.is_enabled()
Query whether document colors are enabled in the given buffer.
Parameters:
{bufnr} (integer?) Buffer handle, or 0 for current. (default: 0)
Return:
(boolean)

Lua module: vim.lsp.utillsp-util

vim.lsp.util.open_floating_preview.Opts
Fields:
{height} (integer) Height of floating window
{width} (integer) Width of floating window
{wrap} (boolean, default:true) Wrap long lines
{wrap_at} (integer) Character to wrap at for computing height when wrap is enabled
{max_width} (integer) Maximal width of floating window
{max_height} (integer) Maximal height of floating window
{focus_id} (string) If a popup with this id is opened, then focus it
{close_events} (table) List of events that closes the floating window
{focusable} (boolean, default:true) Make float focusable.
{focus} (boolean, default:true) Iftrue, and if{focusable} is alsotrue, focus an existing floating window with the same{focus_id}
{offset_x} (integer) offset to add tocol
{offset_y} (integer) offset to add torow
{border} (string|(string|[string,string])[]) overrideborder
{zindex} (integer) overridezindex, defaults to 50
{title} (string|[string,string][])
{title_pos} ('left'|'center'|'right')
{relative} ('mouse'|'cursor'|'editor') (default:'cursor')
{anchor_bias} ('auto'|'above'|'below', default:'auto') Adjusts placement relative to cursor.
"auto": place window based on which side of the cursor has more lines
"above": place the window above the cursor unless there are not enough lines to display the full window height.
"below": place the window below the cursor unless there are not enough lines to display the full window height.
vim.lsp.util.apply_text_document_edit()
apply_text_document_edit({text_document_edit},{index},{position_encoding}) Applies aTextDocumentEdit, which is a list of changes to a single document.
Parameters:
{text_document_edit} (lsp.TextDocumentEdit)
{index} (integer?) Optional index of the edit, if from a list of edits (or nil, if not from a list)
{position_encoding} ('utf-8'|'utf-16'|'utf-32'?)
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocumentEdit
vim.lsp.util.apply_text_edits()
apply_text_edits({text_edits},{bufnr},{position_encoding}) Applies a list of text edits to a buffer.
Parameters:
{text_edits} (lsp.TextEdit[])
{bufnr} (integer) Buffer id
{position_encoding} ('utf-8'|'utf-16'|'utf-32')
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textEdit
vim.lsp.util.apply_workspace_edit()
apply_workspace_edit({workspace_edit},{position_encoding}) Applies aWorkspaceEdit.
Parameters:
{workspace_edit} (lsp.WorkspaceEdit)
{position_encoding} ('utf-8'|'utf-16'|'utf-32') (required)
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#workspace_applyEdit
buf_clear_references({bufnr})vim.lsp.util.buf_clear_references()
Removes document highlights from a buffer.
Parameters:
{bufnr} (integer?) Buffer id
vim.lsp.util.buf_highlight_references()
buf_highlight_references({bufnr},{references},{position_encoding}) Shows a list of document highlights for a certain buffer.
Parameters:
{bufnr} (integer) Buffer id
{references} (lsp.DocumentHighlight[]) objects to highlight
{position_encoding} ('utf-8'|'utf-16'|'utf-32')
See also:
https://microsoft.github.io/language-server-protocol/specification/#textDocumentContentChangeEvent
vim.lsp.util.character_offset()
character_offset({buf},{row},{col},{offset_encoding}) Returns the UTF-32 and UTF-16 offsets for a position in a certain buffer.
Parameters:
{buf} (integer) buffer number (0 for current)
{row} (integer) 0-indexed line
{col} (integer) 0-indexed byte offset in line
{offset_encoding} ('utf-8'|'utf-16'|'utf-32'?) defaults tooffset_encoding of first client ofbuf
Return:
(integer)offset_encoding index of the character in line{row} column{col} in buffer{buf}
vim.lsp.util.convert_input_to_markdown_lines()
convert_input_to_markdown_lines({input},{contents}) Converts any ofMarkedString |MarkedString[] |MarkupContent into a list of lines containing valid markdown. Useful to populate the hover window fortextDocument/hover, for parsing the result oftextDocument/signatureHelp, and potentially others.
Note that if the input is of typeMarkupContent and its kind isplaintext, then the corresponding value is returned without further modifications.
Parameters:
{input} (lsp.MarkedString|lsp.MarkedString[]|lsp.MarkupContent)
{contents} (string[]?) List of strings to extend with converted lines. Defaults to {}.
Return:
(string[]) extended with lines of converted markdown.
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_hover
vim.lsp.util.convert_signature_help_to_markdown_lines()
convert_signature_help_to_markdown_lines({signature_help},{ft},{triggers}) ConvertstextDocument/signatureHelp response to markdown lines.
Parameters:
{signature_help} (lsp.SignatureHelp) Response oftextDocument/SignatureHelp
{ft} (string?) filetype that will be use as thelang for the label markdown code block
{triggers} (string[]?) list of trigger characters from the lsp server. used to better determine parameter offsets
Return (multiple):
(string[]?) lines of converted markdown. (Range4?) highlight range for the active parameter
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_signatureHelp
get_effective_tabstop({bufnr})vim.lsp.util.get_effective_tabstop()
Returns indentation size.
Parameters:
{bufnr} (integer?) Buffer handle, defaults to current
Return:
(integer) indentation size
See also:
'shiftwidth'
vim.lsp.util.locations_to_items()
locations_to_items({locations},{position_encoding}) Returns the items with the byte position calculated correctly and in sorted order, for display in quickfix and location lists.
Theuser_data field of each resulting item will contain the originalLocation orLocationLink it was computed from.
The result can be passed to the{list} argument ofsetqflist() orsetloclist().
Parameters:
{locations} (lsp.Location[]|lsp.LocationLink[])
{position_encoding} ('utf-8'|'utf-16'|'utf-32'?) default to first client of buffer
Return:
(vim.quickfix.entry[]) Seesetqflist() for the format
vim.lsp.util.make_floating_popup_options()
make_floating_popup_options({width},{height},{opts}) Creates a table with sensible default options for a floating window. The table can be passed tonvim_open_win().
Parameters:
{width} (integer) window width (in character cells)
{height} (integer) window height (in character cells)
{opts} (vim.lsp.util.open_floating_preview.Opts?) Seevim.lsp.util.open_floating_preview.Opts.
Return:
(vim.api.keyset.win_config)
vim.lsp.util.make_formatting_params()
make_formatting_params({options}) Creates aDocumentFormattingParams object for the current buffer and cursor position.
Parameters:
{options} (lsp.FormattingOptions?) with validFormattingOptions entries
Return:
(lsp.DocumentFormattingParams) object
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_formatting
vim.lsp.util.make_given_range_params()
make_given_range_params({start_pos},{end_pos},{bufnr},{position_encoding}) Using the given range in the current buffer, creates an object that is similar tovim.lsp.util.make_range_params().
Parameters:
{start_pos} ([integer,integer]?){row,col} mark-indexed position. Defaults to the start of the last visual selection.
{end_pos} ([integer,integer]?){row,col} mark-indexed position. Defaults to the end of the last visual selection.
{bufnr} (integer?) buffer handle or 0 for current, defaults to current
{position_encoding} ('utf-8'|'utf-16'|'utf-32')
Return:
({ textDocument: { uri: lsp.DocumentUri }, range: lsp.Range })
vim.lsp.util.make_position_params()
make_position_params({window},{position_encoding}) Creates aTextDocumentPositionParams object for the current buffer and cursor position.
Parameters:
{window} (integer?)window-ID or 0 for current, defaults to current
{position_encoding} ('utf-8'|'utf-16'|'utf-32')
Return:
(lsp.TextDocumentPositionParams)
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocumentPositionParams
vim.lsp.util.make_range_params()
make_range_params({window},{position_encoding}) Using the current position in the current buffer, creates an object that can be used as a building block for several LSP requests, such astextDocument/codeAction,textDocument/colorPresentation,textDocument/rangeFormatting.
Parameters:
{window} (integer?)window-ID or 0 for current, defaults to current
{position_encoding} ("utf-8"|"utf-16"|"utf-32")
Return:
({ textDocument: { uri: lsp.DocumentUri }, range: lsp.Range })
vim.lsp.util.make_text_document_params()
make_text_document_params({bufnr}) Creates aTextDocumentIdentifier object for the current buffer.
Parameters:
{bufnr} (integer?) Buffer handle, defaults to current
Return:
(lsp.TextDocumentIdentifier)
See also:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocumentIdentifier
vim.lsp.util.make_workspace_params()
make_workspace_params({added},{removed}) Create the workspace params
Parameters:
{added} (lsp.WorkspaceFolder[])
{removed} (lsp.WorkspaceFolder[])
Return:
(lsp.WorkspaceFoldersChangeEvent)
vim.lsp.util.open_floating_preview()
open_floating_preview({contents},{syntax},{opts}) Shows contents in a floating window.
Parameters:
{contents} (table) of lines to show in window
{syntax} (string) of syntax to set for opened buffer
{opts} (vim.lsp.util.open_floating_preview.Opts?) with optional fields (additional keys are filtered withvim.lsp.util.make_floating_popup_options() before they are passed on tonvim_open_win()). Seevim.lsp.util.open_floating_preview.Opts.
Return (multiple):
(integer) bufnr of newly created float window (integer) winid of newly created float window preview window
preview_location({location},{opts})vim.lsp.util.preview_location()
Previews a location in a floating window
behavior depends on type of location:
for Location, range is shown (e.g., function definition)
for LocationLink, targetRange is shown (e.g., body of function definition)
Parameters:
{location} (lsp.Location|lsp.LocationLink)
{opts} (vim.lsp.util.open_floating_preview.Opts?) Seevim.lsp.util.open_floating_preview.Opts.
Return (multiple):
(integer?) buffer id of float window (integer?) window id of float window
rename({old_fname},{new_fname},{opts})vim.lsp.util.rename()
Rename old_fname to new_fname
Existing buffers are renamed as well, while maintaining their bufnr.
It deletes existing buffers that conflict with the renamed file name only when
opts requests overwriting; or
the conflicting buffers are not loaded, so that deleting them does not result in data loss.
Parameters:
{old_fname} (string)
{new_fname} (string)
{opts} (table?) Options:
{overwrite} (boolean)
{ignoreIfExists} (boolean)
vim.lsp.util.show_document()
show_document({location},{position_encoding},{opts}) Shows document and optionally jumps to the location.
Parameters:
{location} (lsp.Location|lsp.LocationLink)
{position_encoding} ('utf-8'|'utf-16'|'utf-32'?)
{opts} (table?) A table with the following fields:
{reuse_win} (boolean) Jump to existing window if buffer is already open.
{focus} (boolean) Whether to focus/jump to location if possible. (defaults: true)
Return:
(boolean)true if succeeded
vim.lsp.util.symbols_to_items()
symbols_to_items({symbols},{bufnr},{position_encoding}) Converts symbols to quickfix list items.
Parameters:
{symbols} (lsp.DocumentSymbol[]|lsp.SymbolInformation[]) list of symbols
{bufnr} (integer?) buffer handle or 0 for current, defaults to current
{position_encoding} ('utf-8'|'utf-16'|'utf-32'?) default to first client of buffer
Return:
(vim.quickfix.entry[]) Seesetqflist() for the format

Lua module: vim.lsp.loglsp-log

Thevim.lsp.log module provides logging for the Nvim LSP client.
When debugging language servers, it is helpful to enable extra-verbose loggingof the LSP client RPC events. Example:
vim.lsp.set_log_level 'trace'require('vim.lsp.log').set_format_func(vim.inspect)
Then try to run the language server, and open the log with:
:lua vim.cmd('tabnew ' .. vim.lsp.get_log_path())
(Or use:LspLog if you have nvim-lspconfig installed.)
Note:
Remember to DISABLE verbose logging ("debug" or "trace" level), else you may encounter performance issues.
"ERROR" messages containing "stderr" only indicate that the log was sent to stderr. Many servers send harmless messages via stderr.
get_filename()vim.lsp.log.get_filename()
Returns the log filename.
Return:
(string) log filename
get_level()vim.lsp.log.get_level()
Gets the current log level.
Return:
(integer) current log level
set_format_func({handle})vim.lsp.log.set_format_func()
Sets formatting function used to format logs
Parameters:
{handle} (function) function to apply to logging arguments, pass vim.inspect for multi-line formatting
set_level({level})vim.lsp.log.set_level()
Sets the current log level.
Parameters:
{level} (string|integer) One ofvim.log.levels
should_log({level})vim.lsp.log.should_log()
Checks whether the level is sufficient for logging.
Parameters:
{level} (integer) log level
Return:
(boolean) true if would log, false if not

Lua module: vim.lsp.rpclsp-rpc

vim.lsp.rpc.PublicClient Client RPC object
Fields:
{request} (fun(method: string, params: table?, callback: fun(err?: lsp.ResponseError, result: any), notify_reply_callback?: fun(message_id: integer)):boolean,integer?) Seevim.lsp.rpc.request()
{notify} (fun(method: string, params: any): boolean) Seevim.lsp.rpc.notify()
{is_closing} (fun(): boolean) Indicates if the RPC is closing.
{terminate} (fun()) Terminates the RPC client.
connect({host_or_path},{port})vim.lsp.rpc.connect()
Create a LSP RPC client factory that connects to either:
a named pipe (windows)
a domain socket (unix)
a host and port via TCP
Return a function that can be passed to thecmd field forvim.lsp.start().
Parameters:
{host_or_path} (string) host to connect to or path to a pipe/domain socket
{port} (integer?) TCP port to connect to. If absent the first argument must be a pipe
Return:
(fun(dispatchers: vim.lsp.rpc.Dispatchers): vim.lsp.rpc.PublicClient)
format_rpc_error({err})vim.lsp.rpc.format_rpc_error()
Constructs an error message from an LSP error object.
Parameters:
{err} (table) The error object
Return:
(string) error_message The formatted error message
notify({method},{params})vim.lsp.rpc.notify()
Sends a notification to the LSP server.
Parameters:
{method} (string) The invoked LSP method
{params} (table?) Parameters for the invoked LSP method
Return:
(boolean)true if notification could be sent,false if not
vim.lsp.rpc.request()
request({method},{params},{callback},{notify_reply_callback}) Sends a request to the LSP server and runs{callback} upon response.
Parameters:
{method} (string) The invoked LSP method
{params} (table?) Parameters for the invoked LSP method
{callback} (fun(err: lsp.ResponseError?, result: any)) Callback to invoke
{notify_reply_callback} (fun(message_id: integer)?) Callback to invoke as soon as a request is no longer pending
Return (multiple):
(boolean) successtrue if request could be sent,false if not (integer?) message_id if request could be sent,nil if not
vim.lsp.rpc.rpc_response_error()
rpc_response_error({code},{message},{data}) Creates an RPC response tableerror to be sent to the LSP response.
Parameters:
{code} (integer) RPC error code defined, seevim.lsp.protocol.ErrorCodes
{message} (string?) arbitrary message to send to server
{data} (any?) arbitrary data to send to server
Return:
(lsp.ResponseError)
See also:
lsp.ErrorCodes Seevim.lsp.protocol.ErrorCodes
start({cmd},{dispatchers},{extra_spawn_params})vim.lsp.rpc.start() Starts an LSP server process and create an LSP RPC client object to interact with it. Communication with the spawned process happens via stdio. For communication via TCP, spawn a process manually and usevim.lsp.rpc.connect()
Parameters:
{cmd} (string[]) Command to start the LSP server.
{dispatchers} (table?) Dispatchers for LSP message types.
{notification} (fun(method: string, params: table))
{server_request} (fun(method: string, params: table): any?, lsp.ResponseError?)
{on_exit} (fun(code: integer, signal: integer))
{on_error} (fun(code: integer, err: any))
{extra_spawn_params} (table?) Additional context for the LSP server process.
{cwd} (string) Working directory for the LSP server process
{detached} (boolean) Detach the LSP server process from the current process
{env} (table<string,string>) Additional environment variables for LSP server process. Seevim.system()
Return:
(vim.lsp.rpc.PublicClient) Seevim.lsp.rpc.PublicClient.

Lua module: vim.lsp.protocollsp-protocol

vim.lsp.protocol.make_client_capabilities()
make_client_capabilities() Gets a new ClientCapabilities object describing the LSP client capabilities.
Return:
(lsp.ClientCapabilities)
Methodsvim.lsp.protocol.Methods
LSP method names.
See also:
https://microsoft.github.io/language-server-protocol/specification/#metaModel
vim.lsp.protocol.resolve_capabilities()
resolve_capabilities({server_capabilities}) Creates a normalized object describing LSP server capabilities.
Parameters:
{server_capabilities} (table) Table of capabilities supported by the server
Return:
(lsp.ServerCapabilities?) Normalized table of capabilities
Main
Commands index
Quick reference

QUICKSTART
DEFAULTS
BUFFER-LOCAL DEFAULTS
GLOBAL DEFAULTS
CONFIG
FAQ
LSP API
VIM.LSP.PROTOCOL
LSP HIGHLIGHT
LSP SEMANTIC HIGHLIGHTS
EVENTS
Lua module: vim.lsp
Lua module: vim.lsp.client
Lua module: vim.lsp.buf
Lua module: vim.lsp.diagnostic
Lua module: vim.lsp.codelens
Lua module: vim.lsp.completion
Lua module: vim.lsp.inlay_hint
Lua module: vim.lsp.semantic_tokens
Lua module: vim.lsp.document_color
Lua module: vim.lsp.util
Lua module: vim.lsp.log
Lua module: vim.lsp.rpc
Lua module: vim.lsp.protocol

[8]ページ先頭

©2009-2025 Movatter.jp