aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc
diff options
context:
space:
mode:
authorMaria José Solano <majosolano99@gmail.com>2024-02-19 18:28:07 -0800
committerLewis Russell <me@lewisr.dev>2024-03-06 19:37:20 +0000
commit0101bdaa1ad8b09ebd5ef5551faf077f39be238c (patch)
tree228e8fee6e039c4df5614f0354f2b49f3285657f /runtime/doc
parent191cca2566a8afe2b2f2744f3eb763d810cc416c (diff)
downloadrneovim-0101bdaa1ad8b09ebd5ef5551faf077f39be238c.tar.gz
rneovim-0101bdaa1ad8b09ebd5ef5551faf077f39be238c.tar.bz2
rneovim-0101bdaa1ad8b09ebd5ef5551faf077f39be238c.zip
docs(lsp): nits and typos in client.lua
Diffstat (limited to 'runtime/doc')
-rw-r--r--runtime/doc/lsp.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/runtime/doc/lsp.txt b/runtime/doc/lsp.txt
index aa56f8bbae..9b1f2d67cd 100644
--- a/runtime/doc/lsp.txt
+++ b/runtime/doc/lsp.txt
@@ -937,7 +937,7 @@ Lua module: vim.lsp.client *lsp-client*
• {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
+ key being the request id while the value is a
table with `type`, `bufnr`, and `method`
key-value pairs. `type` is either "pending"
for an active request, or "cancel" for a
@@ -950,7 +950,7 @@ Lua module: vim.lsp.client *lsp-client*
|vim.lsp.start_client()|. See
|vim.lsp.ClientConfig|.
• {server_capabilities} (`lsp.ServerCapabilities?`) Response from the
- server sent on initialize` describing the
+ server sent on `initialize` describing the
server's capabilities.
• {progress} (`vim.lsp.Client.Progress`) A ring buffer
(|vim.ringbuf()|) containing progress messages
@@ -1000,9 +1000,9 @@ Lua module: vim.lsp.client *lsp-client*
Sends a request to the server. This is a thin
wrapper around {client.rpc.request} with some
additional checking. If {handler} is not
- specified, If one is not found there, then an
- error will occur. Returns: {status},
- {[client_id]}. {status} is a boolean
+ specified and if there's no respective global
+ handler, then an error will occur. Returns:
+ {status}, {[client_id]}. {status} is a boolean
indicating if the notification was successful.
If it is `false`, then it will always be
`false` (the client has shutdown). If {status}