-
-
Notifications
You must be signed in to change notification settings - Fork 961
F.A.Q
Here are some common problems that you may need to understand when working with coc.nvim.
copilot.vim remaps your <tab>
, it checks pumvisible
but not coc#pum#visible
, so it not work well with the custom popup menu.
You can disable the overwrite and define the <tab>
to meet your need, like:
let g:copilot_no_tab_map = v:true
inoremap <silent><expr> <TAB>
\ coc#pum#visible() ? coc#pum#next(1):
\ exists('b:_copilot.suggestions') ? copilot#Accept("\<CR>") :
\ CheckBackSpace() ? "\<Tab>" :
\ coc#refresh()
use <C-e>
to cancel the popup menu(if it's not remapped).
Use autocmd like:
autocmd User EasyMotionPromptBegin :let b:coc_diagnostic_disable = 1
autocmd User EasyMotionPromptEnd :let b:coc_diagnostic_disable = 0
Most color scheme clears existing highlights when loaded, make
sure set your highlights with ColorScheme
autocmd, like:
autocmd ColorScheme * call Highlight()
function! Highlight() abort
hi Conceal ctermfg=239 guifg=#504945
hi CocSearch ctermfg=12 guifg=#18A3FF
endfunction
And you have to use nested autocmd to make ColorScheme
autocmd
fired when using autocmd to change color scheme.
autocmd vimenter * ++nested colorscheme gruvbox
CocMenuSel
is used for highlight select item, the highlight group uses background color from PmenuSel
.
However, many color schemes not considered other highlights inside it.
You can change the highlight group by:
hi CocMenuSel ctermbg=237 guibg=#13354A
in your vimrc, to survive after color scheme change, use:
autocmd ColorScheme * hi CocMenuSel ctermbg=237 guibg=#13354A
The buffer source only provide keywords from buffers meet these conditions:
- Use
bufloaded()
function to check if a buffer is loaded. - The
buftype
option should be empty, check it by:echo getbufvar(bufnr, "&buftype")
.
Use let g:coc_node_path = '/path/to/node'
to make coc.nvim use custom node executable.
You can't, there's no such function provided for omnifunc
option, because vim's omnifunc always block and LSP features like triggerCharacters and incomplete response can't work.
If you want to manually trigger completion add "suggest.autoTrigger": "none",
to coc-settings.json and bind a trigger key like:
inoremap <silent><expr> <c-space> coc#refresh()
Note that some terminals send <NUL>
when you press <c-space>
, so you could use instead:
inoremap <silent><expr> <NUL> coc#refresh()
- Make sure you have
set hidden
in your.vimrc
. - Use
CocActionAsync
instead ofCocAction
in your autocmd, except forBufWritePre
. - Use
CocRequestAsync
instead ofCocRequest
when possible.
Some language servers don't work when the buffer not saved to disk. This is because they only tested on VSCode which always create file before create buffer.
Save the buffer to disk and restart coc.nvim server by :CocRestart
to make the language server work.
By default, coc doesn't show diagnostics in UI when you're in insert mode,
add "diagnostic.refreshOnInsertMode": true
in settings file to enable refresh on insert mode.
If there are other signs that have higher offset, sign of coc.nvim can't be shown. You can change the offset of coc.nvim's signs by add "diagnostic.signOffset": 9999999
to your coc-settings.json to make it higher priority. The default value is 1000. You can also change the signcolumn
option (available with latest neovim) like: set signcolumn=auto:2
.
Some language servers can be slow for receiving document change before trigger completion. You can change the wait time for language server to finish the document change process before completion by changing suggest.triggerCompletionWait
in your coc-settings.json
, it's default to 50
in milliseconds.
Some plugins like Ultisnips and vim-closer would remap your <tab>
or <cr>
without configuration. You can check out your key-mapping by command like :verbose imap <tab>
.
- Enter these commands:
:profile start profile.log :profile func * :profile file *
- Make issue happen.
- Run command
:profile stop
(neovim only). - Exit vim, and open the newly generated profile.log file in your current directory.
To get the communication between vim and coc.nvim
- Add
let g:node_client_debug = 1
in your vimrc. - Restart vim and make issue happen.
- Use command
:call coc#client#open_log()
to open log file, or use:echo $NODE_CLIENT_LOG_FILE
to get file path of log.
Enable debug mode for coc.nvim by environment variable:
let $NVIM_COC_LOG_LEVEL = 'trace'
Open log file by command:
:CocOpenLog
This is done by the doHover
action. Configure a mapping like, e.g.:
nnoremap <silent> <leader>h :call CocActionAsync('doHover')<cr>
Possible bug with guicursor
option on your terminal, you can disable transparent cursor by
let g:coc_disable_transparent_cursor = 1
in your .vimrc.
It's expected since the float windows/popups are absolutely positioned.
- For documentation of completion, use
"suggest.floatEnable": false
in settings.json. - For diagnostic messages, use
"diagnostic.messageTarget": "echo"
in settings.json. - For signature help, use
"signature.target": "echo"
in settings.json. - For documentation on hover, use
"hover.target": "echo"
in settings.json.
The default highlight group linked by CocFloating
could have reverse
attribute, you will have colored background for some texts on that case, define your own CocFloating
highlight group on that case.
hi link CocFloating Normal
Checkout :h coc#float#has_scroll()
Focus the window by <C-w>w
if it's focusable on neovim and invoke :call CocAction('openlink')