You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm having trouble where the rainbow plugin where it overrides the syntax highlighting on https://github.com/elzr/vim-json. Ideally, I'd like it to show up in red if there is a missing comma.
I think this can be done with the existing options for rainbow, but I cannot figure it out. I would appreciate your help, I barely know vim code.
Describe the solution you'd like
I would like a config that allows me to use both this plugin and https://github.com/elzr/vim-json, while retaining the syntax error highlighting of that plugin.
Describe alternatives you've considered
I've tried to come up with it on my own, and I couldn't figure it out and need to move on.
Additional context
I'm using the default rainbow config.
Example json I would like to have the errors show up on (missing a comma):
[
{
}
{
}
]
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm having trouble where the rainbow plugin where it overrides the syntax highlighting on https://github.com/elzr/vim-json. Ideally, I'd like it to show up in red if there is a missing comma.
I think this can be done with the existing options for rainbow, but I cannot figure it out. I would appreciate your help, I barely know vim code.
Describe the solution you'd like
I would like a config that allows me to use both this plugin and https://github.com/elzr/vim-json, while retaining the syntax error highlighting of that plugin.
Describe alternatives you've considered
I've tried to come up with it on my own, and I couldn't figure it out and need to move on.
Additional context
I'm using the default rainbow config.
Example json I would like to have the errors show up on (missing a comma):
The text was updated successfully, but these errors were encountered: