Ansible Vim Versions Save

A vim plugin for syntax highlighting Ansible's common filetypes

3.4

4 months ago

What's Changed

  • Add custom highlighting for the common FQCN names
    • Thanks to @gardar for kicking off this change via #136 !

3.3

10 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/pearofducks/ansible-vim/compare/3.2...3.3

3.2

2 years ago
  • ansible_with_keywords_highlight is soft-deprecated (there is backwards compatibility in place for now), and is replaced with ansible_loop_keywords_highlight which aligns better with modern Ansible keywords for loops
  • Keywords that have been removed from Ansible are no longer highlighted, and new keywords in latest Ansible are added

3.1

2 years ago

Thanks to @pescobar the snippet-generation script now supports fully qualified collection names when used against Ansible 2.10 or greater.

https://docs.ansible.com/ansible/latest/user_guide/collections_using.html

3.0

3 years ago

Breaking: Drops Python 2 support in UltiSnip generation

Change: Makes the UltiSnip snippets generation reproducible

2.2

3 years ago

Add highlighting for the loop keyword, which has been available since Ansible 2.5.

https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html

2.1

4 years ago

Notable changes:

  • python3 support added to the UltiSnip generate.py, as well as Mac Homebrew support
  • an old regexpengine workaround was removed that was breaking some setups

Otherwise there were minor fixes included in this changeset.

2.0

5 years ago

The filetype for playbooks is now set to yaml.ansible.

  • Using a compound filetype here improves compatibility with some other plugins, and is a bit more honest about the filetypes being used. We could set it to yaml.jinja2.ansible, if there are strong opinions on this please open an issue.
  • This only breaks setups using vim plugin on-demand loading features — e.g. { 'for': 'ansible' } in vim-plug. Otherwise this change should not break anything.

g:ansible_extra_syntaxes is deprecated in favor of g:ansible_template_syntaxes — which will use conditional compound filetypes, instead of sourcing all filetypes listed and hiding them under ansible_template.

  • While this is a complete deprecation of one setting, the new functionality is significantly better all around and should support the same use-cases.
  • Example: a ruby+ansible-template will have a filetype of ruby.jinja2 instead of ansible_template

One non-breaking change is also added, this plugin gains additional compatibility with stephpy/vim-yaml — syntax highlights will be improved when using this plugin.

1.1

5 years ago

DEPRECATED

This is the last version using ansible as the filetype for Ansible playbooks. This tag is created as a convenience for anyone to branch from or keep as their plugin target.

1.0

8 years ago

Changes:

  • hosts files are now highlighted with our own rules, rather than use dosini rules. This allows for much better treatment of variables and Ansible's special categories (e.g. [foo:vars]).