vim version: NVIM v0.4.0-dev
node version: v12.6.0
coc.nvim version: 0.0.73-56825890dc
term: screen-256color
platform: linux
Messages
Error detected while processing function startify#open_buffers[6]..223_open_buffer:
line 12:
E325: ATTENTION
44 lines yanked into "+
44 lines yanked into "+
Output channel: prettier
Describe the bug
I'm using coc with SpaceVim and for a few days now I noticed autocomplete, error detection & other features wouldn't work, had now idea why, then I saw there's :CocOpenLog command which gives me this:
I have no idea why since I'm haven't set any coc-settings.json and I haven't touched any additionalKeywords related options in vim scripts either.
Reproduce the bug
Note, if you can't provide minimal vimrc that could reproduce the issue,
it's most likely we can't do anything to help.
Create file mini.vim with:
set nocompatible
set runtimepath^=/path/to/coc.nvim
filetype plugin indent on
syntax on
set hidden
Start (neo)vim with command: vim -u mini.vim
Operate vim.
I ran the above commands. After opening a main.cpp file as test, the output of :CocOpenLog is:
2019-07-31T10:41:32.655 ERROR (pid:18633) [workspace] - Error on create buffer: TypeError: this._additionalKeywords is not iterable
at Document.setIskeyword (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:49901:29)
at Document.init (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:49893:14)
at processTicksAndRejections (internal/process/task_queues.js:85:5)
at async Workspace.onBufCreate (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:45317:27)
at async Promise.all (index 0)
at async Workspace.attach (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:45236:9)
at async Workspace.init (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:44171:9)
at async Plugin.init (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:54171:13)
at async /home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:1799:13
2019-07-31T10:41:32.756 INFO (pid:18633) [plugin] - coc 0.0.73-56825890dc initialized with node: v12.6.0
2019-07-31T10:41:49.565 ERROR (pid:18633) [workspace] - Error on create buffer: TypeError: this._additionalKeywords is not iterable
at Document.setIskeyword (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:49901:29)
at Document.init (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:49893:14)
at processTicksAndRejections (internal/process/task_queues.js:85:5)
at async Workspace.onBufCreate (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:45317:27)
at async Promise.all (index 0)
at async Events.fire (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:37467:17)
at async NeovimClient.<anonymous> (/home/razvan/.cache/vimfiles/repos/github.com/neoclide/coc.nvim/build/index.js:1755:17)
Screenshots (optional)
As can be seen in the image the's even errors in main.cpp but coc can't detect anything, probably the process doesn't start at all.
Result from CocInfo
versions
vim version: NVIM v0.4.0-dev node version: v12.6.0 coc.nvim version: 0.0.73-56825890dc term: screen-256color platform: linux
Messages
Error detected while processing function startify#open_buffers[6]..223_open_buffer:
line 12:
E325: ATTENTION
44 lines yanked into "+
44 lines yanked into "+
Output channel: prettier
Describe the bug
I'm using coc with SpaceVim and for a few days now I noticed autocomplete, error detection & other features wouldn't work, had now idea why, then I saw there's
:CocOpenLog
command which gives me this:while running
NVIM_COC_LOG_LEVEL=debug nvim
I have no idea why since I'm haven't set any
coc-settings.json
and I haven't touched anyadditionalKeywords
related options in vim scripts either.Reproduce the bug
Note, if you can't provide minimal vimrc that could reproduce the issue, it's most likely we can't do anything to help.
Create file
mini.vim
with:Start (neo)vim with command:
vim -u mini.vim
Operate vim.
I ran the above commands. After opening a
main.cpp
file as test, the output of:CocOpenLog
is:Screenshots (optional)
As can be seen in the image the's even errors in
main.cpp
but coc can't detect anything, probably the process doesn't start at all.Thanks for the tool though, it's really awesome!