Tip #411: How to initialize plugins

Plugins have two basic ways of being initialized:

    a) via some variable that the plugin script uses;
       the initialization here is obvious -- set the
       desired variables in your <.vimrc> (or use
       an appropriate autocmd to do so).

    b) via a map or function call.  The problem here
       is that <.vimrc> is sourced prior to plugin
       sourcing, so the map or function call isn't
       available yet.

       Solution: put in .vim/after/plugin a file
       of the same name as the plugin you're initializing.
       In that file put

            call TheInitializationFunction()

            -or-

            norm TheInitializationMap

For example, the <HiMtchBrkt.vim> script which supports the
highlighting of matching brackets as you move onto a
bracket is not on by default.  Normally it requires one to
type "\[i" to start it.  However, if you'd like to have the
script to start enabled, then put

            norm \[i

into the file <.vim/after/plugin/HiMtchBrkt.vim> (see tip
vimtip#177).

(Windows users: mentally change .vim to _vimfiles and / to \
in the tip above)



<< Allow Inform header files to be distinguished from C headers | Easy menu-style switch between files with a simple map >>

Additional Notes