Closed yuki-yano closed 2 years ago
Reproduced. But it is intended behavior. I can change the implementation, but it has the side effects.
If you want to overwrite ftplugin options, you should use after/ftplugin
instead.
I understand.
I will try to handle this by using after/ftplugin
or another event.
I have removed ftplugin reset. But it is the test. I may revert the changes.
I have reverted the changes. filetype plugin reset is needed to load ftplugins lazily!
So this is your configuration problem. I cannot help.
Problems summary
If a lazy loaded plugin( use
on_ft
) containsftplugin
orafter/ftplugin
, the result of:verbose autocmd FileType
for that ft will change so thats:LoadFTPlugin()
ignores what I wrote in the vimrc and runs last.Expected
When a plugin is lazy loaded,
s:LoadFTPlugin()
is executed first.Environment Information
dein.vim version(SHA1):
00bb3a1ddb601c7500ab541d968a9b6035fc2086
OS: macOS Big Sur 11.6.1
neovim/Vim
:version
output:Features: +acl +iconv +tui See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim" fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-e4e0e8c_1/share/nvim"
How to reproduce the problem from neovim/Vim startup
vim
ortypescript
fileverbose set formatoptions
verbose autocmd FileType