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
It would be nice and consistent to be able to configure g:ansible_extra_keywords_highlight like g:ansible_normal_keywords_highlight and g:ansible_with_keywords_highlight. I'd like them all with the same style.
An easy way would be to define a sane default style for g:ansible_extra_keywords_highlight (Identifier I suppose), and allow the user to use a style instead of just "1" to enable a second pre-defined style.
I could be extended to g:ansible_name_highlight and g:ansible_attribute_highlight. For instance I would really like to set ansible_name_highlight on Tag instead of Underlined.
The text was updated successfully, but these errors were encountered:
I agree with you and do have plans to unify them under the same style at some point. Unfortunately since this is a major breaking-change (or at the very least a change in how this is all handled) I'd like to take it in phases somehow.
The reason this hasn't been done yet is at v2 I switched to the compound syntax, and wanted to avoid too many changes at once.
I admit I don't know anything in vim script. Would it be difficult to make it reverse compatible with the current syntax? I mean, you can try to catch "if it's 'd' or 'b' then use predefined style for dim or brighten, else it should be directly the style name".
Hi,
It would be nice and consistent to be able to configure
g:ansible_extra_keywords_highlight
likeg:ansible_normal_keywords_highlight
andg:ansible_with_keywords_highlight
. I'd like them all with the same style.An easy way would be to define a sane default style for
g:ansible_extra_keywords_highlight
(Identifier
I suppose), and allow the user to use a style instead of just "1" to enable a second pre-defined style.I could be extended to
g:ansible_name_highlight
andg:ansible_attribute_highlight
. For instance I would really like to setansible_name_highlight
onTag
instead ofUnderlined
.The text was updated successfully, but these errors were encountered: