Customization

Customization

Adding a new plugin, color-scheme, ...

To add a new plugin, a new color-scheme or anything else, you should do that using git sub-modules, you should only use the custom group located at vimius/vim/custom for the your custom stuff.

The custom group will be loaded before any other group, except of course the core group, this will ensure that your version of any already-installed plugin will be loaded instead, so for example, if you have a new version (or another fork) of a plugin, just add it to your custom folder and will be loaded first.

Disabling a plugin

Vimius makes it too easy to disable any included plugin, color-scheme, lang etc.. Disabling a plug-in is done withing your ~/.vimrc.before file using the vimius#disable_plugin() method. This methods takes two arguments, the plugin name and optionally the reason for disabling the plugin, if reason is given, all bindings that Vimius binds to the plugin, will still be bind but the action will just be an echo that the plugin is disabled, so for example:

Vimius adds the binding <C-t> or <D-t> on MacVim to open Command-t plugin which requires Vim built with ruby support. If your Vim is not built with ruby support, your Vim will not throw errors about it because Vimius will disable the plugin automatically, however you try <C-t> or <D-t> (you might expect that nothing happens but..) the following message appears in the command-line area:

The plugin command-t is disabled for the following reason: Vim is compiled without ruby support.

" Disable a plugin
"
" @param [String] The plugin name
" @param [String] The reason why it is disabled
" @return [Bool]
function! vimius#disable_plugin(...)
endfunction