ansible-vim
ansible-vim copied to clipboard
A vim plugin for syntax highlighting Ansible's common filetypes
I'm using this minimal vimrc: ```vim set nocp call plug#begin('~/.vim/plugged') Plug 'pearofducks/ansible-vim' call plug#end() filetype plugin indent on syntax on set ai set si ``` and I get the following...
Here, `ansible.netcommon.ipv4` should have the same highlighting as the `combine()` filter:  Perhaps worth adjusting the regexp.
Hi, 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...
Are there any plans/interest of adding completion/autocompletion of ansible module names, options and common args. or is would that be better served in a different plugin? I'm imagining it could...
This one is really frustrating me. Load the plugin how you like (I use pathogen still), then: ``` let g:ansible_unindent_after_newline = 1 let g:ansible_attribute_highlight = "ob" let g:ansible_extra_keywords_highlight = 1...
When opening a yml file with this plugin enabled, I see only: `---2;2R^[[>1;5200;0c^[]10;rgb:2e2e/3434/3636^G^[]11;rgb:ffff/ffff/ffff^G` This stays for a second or two and then the rest of the file appears. A clear...
This refines the matching for the name key to only target instances where it's an item in a list. This change significantly reduces the likelihood of false positives. Related Issue:...
I just upgraded to neovim, and using these options: ```lua vim.api.nvim_create_autocmd({ "BufRead", "BufNewFile" }, { pattern = { "*/ansible/*.yml", "*/tasks/*.yml", }, callback = function() vim.bo.filetype = "ansible" end }) --...