-
Notifications
You must be signed in to change notification settings - Fork 80
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
Use ft=dockerfile? (lowercase) #67
Comments
Hm, I believe there's no particular reason for than except the historical one. |
The reason for change that to the original vim behavior is that other plugins, which working on this filetype doesn't work without additional fixes in the vimrc. Best regards |
ekalinin/Dockerfile.vim uses Dockerfile as a filetype, causing hadolint not to be activated when editing Dockerfile files. nvim-lspconfig also uses both filetypes for activating dockerls, so I think it makes sense to have them both for hadolint too until this is eventually changed in Dockerfile.vim. (see linked issue) See: https://github.com/neovim/nvim-lspconfig/blob/cd1ccf0/lua/lspconfig/dockerls.lua#L10 ekalinin/Dockerfile.vim#67
ekalinin/Dockerfile.vim uses Dockerfile as a filetype, causing hadolint not to be activated when editing Dockerfile files. nvim-lspconfig also uses both filetypes for activating dockerls, so I think it makes sense to have them both for hadolint too until this is eventually changed in Dockerfile.vim. (see linked issue) See: https://github.com/neovim/nvim-lspconfig/blob/cd1ccf0/lua/lspconfig/dockerls.lua#L10 ekalinin/Dockerfile.vim#67
Only as an FYI, not knowing the best way to proceed, however, the filetype |
Just ran into this issue as well. :-( It is breaking tree_sitter which is trying to load a compiled library called The workaround for me is to override treesitter as follows: vim.treesitter.language.register("dockerfile", "Dockerfile") |
Vim itself uses
filetype=dockerfile
, whereasDockerfile
is used here.Is there a specific reason for this? I think it should/could use the default filetype here also.
(Via neomake/neomake#2498)
The text was updated successfully, but these errors were encountered: