Skip to content
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

epuppet filetype detection does not match subtype via file content header or path in vim #148

Open
lelutin opened this issue Aug 28, 2024 · 0 comments

Comments

@lelutin
Copy link
Collaborator

lelutin commented Aug 28, 2024

in #146 @shadowwa worked on implementing subtype detection for epuppet so that we can have both syntax and other goodies for the epuppet tags and the underlying text.

However, one of the features was working correctly with neovim, but not with vim: that of reusing the builtin filetype detection in order to match when some parts of the content or the path to the file identify what type of file we're using.

We need to look into uncommenting the tests for those two kinds of filetype detection and then fixing that for vim

Note: the previous attempt by @shadowwa was to call out to doautocmd filetypedetect BufRead + the filename without the .epp extension during the BufRead,BufNewFile autocommand for *.epp. This did not work since the autocmd would call setf something, but that would result in nothing since the filetype was already set to epuppet at that time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant