A.J.Mechelynck wrote:
[...]
IU mentioned the VimEnter event, which is triggered at the very end of
startup. It is of course possible that other scripts than your own will
set up VimEnter autocommands to create new autocommands in their turn,
but IMHO it is highly unlikely.
[...]
Oops, sorry,
A.J.Mechelynck wrote:
A.J.Mechelynck wrote:
[...]
IU mentioned the VimEnter event, which is triggered at the very end of
startup. It is of course possible that other scripts than your own
will set up VimEnter autocommands to create new autocommands in their
turn, but IMHO it is highly
Elliot Shank wrote:
[...]
It still looks like my only option is to try to be the absolutely last
plugin loaded.
Try naming it (on Windows) ~/vimfiles/after/plugin/last.vim or (on
Unix) ~/.vim/after/plugin/last.vim
In most cases, plugins in a single directory will be sourced
