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
But the plugin is always overwriting the setting filetype to yaml.ansible, I would like to use only filetype ansible for "*/tasks/*.yml", any idea how to do this?
How could this maybe be overwriting using the after dir?
If I add this to every file: # vim: set ft=ansible: works but I would like to prevent don't it.
The main problem that I have is that if I use yaml.ansible for an unknown reason I don't see the jinjaVarBlock
This is how I see it with ft=yaml.ansible
And I I use ft=ansible:
I notice that when using ft=yaml.ansible the :syn list is empty but when using only ft=ansible I get all the syntax groups
The text was updated successfully, but these errors were encountered:
nbari
changed the title
neovim, how to keep ft=ansible instead of ft=yaml.ansible
neovim, how to keep ft=ansible instead of ft=yaml.ansible (mising jinjaVarBlock)
Sep 24, 2023
I just upgraded to neovim, and using these options:
For the LSP using
ansiblels
I use this:But the plugin is always overwriting the setting filetype to
yaml.ansible
, I would like to use only filetypeansible
for"*/tasks/*.yml"
, any idea how to do this?How could this maybe be overwriting using the
after
dir?If I add this to every file:
# vim: set ft=ansible:
works but I would like to prevent don't it.The main problem that I have is that if I use
yaml.ansible
for an unknown reason I don't see thejinjaVarBlock
This is how I see it with
ft=yaml.ansible
And I I use
ft=ansible
:I notice that when using
ft=yaml.ansible
the:syn list
is empty but when using onlyft=ansible
I get all the syntax groupsThe text was updated successfully, but these errors were encountered: