leigh/nvim-cmp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add slow down reason

Browse Source
This commit is contained in:
hrsh7th
2021-08-29 15:35:04 +09:00
parent a339421f4b
commit 63d3199cfd
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -397,14 +397,16 @@ cmp.setup {
I've optimized `nvim-cmp` as much as possible, but there are currently some known / unfixable issues. I've optimized `nvim-cmp` as much as possible, but there are currently some known / unfixable issues.
1. `cmp-buffer` source and too large buffer 1. `cmp-buffer` source and too large buffer
The `cmp-buffer` source makes index of the current buffer so if the current buffer is too large, will be slowdown main UI thread. The `cmp-buffer` source makes index of the current buffer so if the current buffer is too large, will be slowdown main UI thread.
1. some language servers 1. some language servers
For example, `typescript-language-server` will returns 15k items to the client. For example, `typescript-language-server` will returns 15k items to the client.
In such case, the time near the 100ms will be consumed just to parse payloads as JSON. In such case, the time near the 100ms will be consumed just to parse payloads as JSON.
1. You set `vim.lsp.set_log_level` up by yourself.
This setting will cause the filesystem operation for each LSP payloads.
This will extremely slow down nvim-cmp (and other LSP related features.)
#### How to setup supertab-like mapping? #### How to setup supertab-like mapping?
This is supertab-like mapping for [LuaSnip](https://github.com/L3MON4D3/LuaSnip) This is supertab-like mapping for [LuaSnip](https://github.com/L3MON4D3/LuaSnip)