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
{{ message }}
This repository has been archived by the owner on May 6, 2024. It is now read-only.
This may be a fundamental limitation of this approach rather than a bug that should be fixed, but I wanted to report it nevertheless (especially considering the possibility of upstreaming it):
When filetype.nvim is installed, it (correctly) disables the built-in filetype.vim. However, it also disables all ftdetect/foo.vim in runtimepath, which means that filetype plugins like https://github.com/lervag/vimtex which extend or correct Vim's detection logic no longer work.
Of course, I can mirror what the plugin's ftdetect/ scripts are doing in my setup, but a more conservative (and still as performant) approach would be to disable only filetype.vim but keep sourcing ftdetect/ scripts (which, however, may require changes in core so be only relevant for an upstream version).
The text was updated successfully, but these errors were encountered:
This may be a fundamental limitation of this approach rather than a bug that should be fixed, but I wanted to report it nevertheless (especially considering the possibility of upstreaming it):
When
filetype.nvim
is installed, it (correctly) disables the built-infiletype.vim
. However, it also disables allftdetect/foo.vim
inruntimepath
, which means that filetype plugins like https://github.com/lervag/vimtex which extend or correct Vim's detection logic no longer work.Of course, I can mirror what the plugin's
ftdetect/
scripts are doing in my setup, but a more conservative (and still as performant) approach would be to disable onlyfiletype.vim
but keep sourcingftdetect/
scripts (which, however, may require changes in core so be only relevant for an upstream version).The text was updated successfully, but these errors were encountered: