color_coded
color_coded copied to clipboard
weird unwanted highlight word on every top screen
Here's the thing, after carefully examination which plugin had caused the following issues as below screenshots indicated, finally I find it was color_coded which brings me that weird highlight.
Does anyone know how this happened and how to remove this highlight feature?
a. After used color_coded.
Plugin 'jeaye/color_coded'
![]()
![]()
![]()
b. Before used color_coded.
" Plugin 'jeaye/color_coded'
![]()
![]()
![]()
@myme5261314 Sorry, I don't see the issue here. In your "after color_coded" shots, a couple of things are highlighted.
-
VideoFrameRef
is highlighted and it looks like that's because you have:set hls
enabled; use:set nohls
to disable it; this is not related to color_coded - The various full-caps defines are highlighted, such as
MY_HEIGHT
, which makes sense, since you're using color_coded to highlight your code, I imagine.
So we can be 100% clear, are you 100% what color_coded is supposed to be doing? You're meant to supply it some configuration in a .color_coded
file and it will use that information to compile your code, as you type, and change vim's highlighting to match the semantics of the code. From how it looks, you're using color_coded and you've not provided a valid .color_coded
file, since not many things are actually highlighted.
Please let me know if you have further questions.
I think you have misunderstood my current issue. Maybe a gif record could help the illustration. The weird highlight always take place when the screen scrolls down.
As refer to #63 , using absolute path will give me this.
-x c++ -DDEBUG -I/home/deeplearn/library/caffe/include -I/usr/include/openni2 -I/usr/local/cuda/include -I/usr/local/include -I/project_path/include -Wall -Werror
Using relative path gives me worse highlighting since it couldn't find header file.
-x c++ -DDEBUG -I/home/deeplearn/library/caffe/include -I/usr/include/openni2 -I/usr/local/cuda/include -I/usr/local/include -Iinclude -Wall -Werror
I've pushed up some big changes into master which fixes a number of highlighting issues. Let me know how it goes for you.
@myme5261314 Any update?
@jeaye
Nope, but I found the issue really happens once I put the cursor to the place of left bracket (
or right bracket )
. When the cursor leave that position, the weird highlighted word disappeared.
Please notice the different cursor in normal mode (not mouse cursor I mean, I was putting the cursor at the left bracket in the first image, and i
of int
in the second image) and the weird highlighted word std.
PS: What else plugin of vim which I installed and related to the brackets is wildfire.vim. Maybe it's the conflicts between color_coded and this plugin?