aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc
diff options
context:
space:
mode:
Diffstat (limited to 'runtime/doc')
-rw-r--r--runtime/doc/lsp.txt10
1 files changed, 9 insertions, 1 deletions
diff --git a/runtime/doc/lsp.txt b/runtime/doc/lsp.txt
index e77ad5dcf3..6d232657c9 100644
--- a/runtime/doc/lsp.txt
+++ b/runtime/doc/lsp.txt
@@ -1900,7 +1900,15 @@ you want to trigger on EVERY keypress you can either:
*vim.lsp.completion.enable()*
enable({enable}, {client_id}, {bufnr}, {opts})
Enables or disables completions from the given language client in the
- given buffer. Example: |lsp-attach| |lsp-completion|
+ given buffer. Effects of enabling completions are:
+ • Calling |vim.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-attach| |lsp-completion|
Note: the behavior of `autotrigger=true` is controlled by the LSP
`triggerCharacters` field. You can override it on LspAttach, see