-
Notifications
You must be signed in to change notification settings - Fork 455
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
Poor yaml syntax when using stephpy/vim-yaml (and also Polyglot) #162
Comments
Yaml is supported and works properly using the built-in yaml syntax. Feel free to open a PR which adjusts your syntax highlighting to match the built-in syntax. |
If the issue is that the other plugin defines new syntax groups, then you just need to track those down (in the syntax file you linked) and add new links in the style of |
What's the status of this? Can this be closed now? |
@dsifford it's unfortunate, but most of the comments re: the issue were on the PR. AFAIK, we are still waiting on stephpy/vim-yaml#22 (which, at this point, I don't expect to see fixed). I think, given that the workaround "works," we can close with permission of @TheWall89 If @TheWall89 is bent on using
|
Hi guys. Yes, I'm closing this myself. I'll try to issue a PR to stephpy and, if this is accepted, re-issue a new PR here to color the right groups with Dracula. Bye. |
@TheWall89 if stephpy won't respond, consider forking as I outlined above ^ Best of luck🧛♂️ |
What happened
Syntax highlight is not colouring YAML keys and un-quoted values with different colours.
What I expected to happen
I expect the key to have a different colour than the value.
Screenshot
With
darkblue
theme, syntax is better:Machine Info
vim
/gvim
/neovim
): vimTERM
environment variable: xterm-256colorAdditional Info
I checked out the file yaml.vim. It looks like Dracula uses matches and keyword from the default Vim syntax file for YAML. stephpy/vim-yaml uses different ones: https://github.com/stephpy/vim-yaml/blob/master/after/syntax/yaml.vim .
The text was updated successfully, but these errors were encountered: