-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
function
keyword in javascript breaks highlighting the the succeeding paranthesis
#122
Comments
@Nader-gator will the branch |
it fixed some but not all of the parenthesis and brackets. I fixed this issue myself by disabling some of the parenthesis syntax rules in vim polyglot that was preventing rainbow from highlighting the parentheses. I see that in your new commit you only added |
same issue with vim-polyglot |
Could you please follow this doc to try to solve this confliction? |
I've made some modifications but theres still some bugs. I'll make a PR when its done probably in a couple of weeks |
How do we add this in our vimrc? |
I have had the same issue. when you use the function keyword, the highlighting just don't work |
a workaround for me was switching from vim-javascript to https://github.com/jelera/vim-javascript-syntax |
The plugin works fine in all languages, but when I load javascript, none of the parenthesis inside a function definition are color. i use polyglot and when I disable javascript syntax highlighting(


let g:polyglot_disabled = ['javascript']
) and use the default neovim syntax mode it works fine. so I suspect this language pack that polyglot uses is the culprit but I can't figure out how to fix this. could it possibly be that the language pack is highlighting over the rainbow with its own rules?edit: forgot to add, the same exact problem happens with
()=>{}
syntax as wellThe text was updated successfully, but these errors were encountered: