Closed linjiX closed 5 years ago
What's your system? I can't reproduce on Mac and windows.
I use Ubuntu16.04
Can't reproduce on vim 8.1.1477 with Ubuntu16.04, try upgrade your coc.nvim.
I upgrade my coc, but the issue still exist.
I create a minimal reproduce environment which remove all other vim plugins and coc plugins and a empty coc-settings.json. node --version v10.16.0 Minimal vimrc:
set nocompatible set nobackup
call plug#begin('~/.vim/plug') Plug 'neoclide/coc.nvim', {'branch': 'release'} call plug#end()
filetype plugin indent on syntax enable syntax on
And I found that the error message will also appear in Neovim when yank. And all other things works fine in Neovim
For me, my yank history ($HOME/.config/coc/extensions/coc-yank-data/yank.json
) had become corrupt, ending with an additional ]}]
.
Deleting this solved the problem; doesn't fully solve the issue but it's a temporary fix.
@BodneyC Yes, remove yank.json does fix the error message temporary. I also tried to reproduce this issue in my environment. Here is what I found:
Hope it helps.
The json file is written on TextYankPost, so maybe something wrong with trigger of autocmd on your vim.
I can't reproduce with my vim, no change of yark.json after enter visual mode or scroll.
I think I found the root cause: TextYankPost and visual selection causes spurious syntax highlights I is a vim issue about TextYankPost. I may skip this plug until it is fixed
Thanks
I have the same problem.
Whenever I yank a word in Vim/gVim version 8.1 there is never a highlight timeout. The highlight stays indefinitely, regardless of what I set yank.highlight.duration
to. Also, when I set yank.highlight.duration
to less than 100 ms there is sometimes no highlight at all.
Yanking in NeoVim however times out according to yank.highlight.duration
.
OS: Antergos Linux x86_64
Node version: v12.10.0
Coc.nvim version: 0.0.74-c97d41aa1e
No idea, could be caused by vim option or other plugin, you can disable this feature
This plugin makes some highlight issue and error message in Vim8 And it works fine in Neovim
Issue:
vim --version