New answers tagged ftdetect
0
votes
How to overwrite ftdetect from a plugin loaded with lazy?
I fixed the problem by loading my custom options after the plugin, the order of loading the plugins and custom options matters, I changed my init.lua from:
require("user.options")
require(&...
2
votes
Accepted
How can I avoid built-in filetype detection?
After a lot of trial and error, I found a solution.
It turns out that the order of entries in runtimepath doesn't matter.
All I had to do was use au! instead of au in the plugin's ftdetect/k.vim. ...
2
votes
How can I avoid built-in filetype detection?
You don't generally need to suppress the filetype detection, because (proper) filetype plugins set b:undo_ftplugin and other variables, which Vim uses automatically to "undo" the results of ...
3
votes
How can I avoid built-in filetype detection?
The *.k extension is detected by $VIMRUNTIME/filetype.vim that comes before the ~/.vim/ftdetect/*.vim in the execution list.
That is why you have these scripts being evaluated (kwd.vim calling cpp.vim ...
Top 50 recent answers are included