[Vimoutliner] problem with plugin loading code

[Ross Boylan]

On Tue, 2008-01-29 at 10:17 +0000, Martin DeMello wrote:
> I'm running vim 7.1.213 and vimoutliner 0.34 under Gentoo, both
> installed from portage. In order to get vimoutliner working, I had to
> go to  /usr/share/vim/vimfiles/ftplugin/vo_base.vim and comment out
> everything from
> 
> " let s:tmp = g:vo_modules_load . ':'
> 
> onwards, otherwise it complains about g:vo_modules_load being unknown.
> Grepping through /usr/share/vim confirmed that it was indeed not
> defined anywhere. Am I missing a file?
> 
> martin

On Debian one has to enable particular vim addons explicitly.  I don't
know if that is Debian-specific; at any rate, Gentoo is a Debian
deriviative I think.  From /usr/share/doc/vim/NEWS.Debian.gz:
vim (1:7.1-022+1) unstable; urgency=low

  * /usr/share/vim/addons/ is no longer in the vim runtimepath

    This is intended to avoid arbitrarly clashes among addons installed
    system-wide and enabled by default, and to set up a common ground
for Vim
    extensions of various kinds.  From now on vim addons won't be
enabled by
    default upon installation but will need to be enabled on a per-addon
basis
    either in a system-wide manner (affecting all users of the system)
or by
    each user who wants to use them.  A tool exists for helping with
addon
    management: it is called "vim-addons" and is shipped by the package
    "vim-addon-manager"; all vim addon packages should recommend it.

    For more information see the VIM packaging policy (available on the
web at
    http://pkg-vim.alioth.debian.org/vim-policy.html/index.html) and the
    manual page of vim-addons, available in the vim-addon-manager
package.

 -- Stefano Zacchiroli <zack at debian.org>  Thu, 19 Jul 2007 23:28:44
+0200

Ross