On Thu, Nov 08, 2007 at 10:05:23AM +0100, Markus Fischer wrote: > Version: 1:7.0-122+1etch3 > > The directory /usr/share/vim/addons/ is never considered by vim to be > parsed upon starting. Using strace I discovered that only > /var/lib/vim/addons/ is considered.
For the version of Vim you reported the bug against, /usr/share/vim/addons/ is still included in Vim's "runtimepath" option by default. If Vim isn't checking that directory, then you likely have modified /usr/share/vim/vim70/debian.vim or are overriding the value in your ~/.vimrc. You can check where that option was last set by starting Vim and then using the command ":verbose set runtimepath?". In case you happen to be running reportbug on an older system than where you experienced the problem, I'll explain the situation for Lenny/Sid as well. We still expect packages that ship Vim plugins to install those plugins in /usr/share/vim/addons (or a path specific for their package) but we no longer include that path by default in Vim's runtimepath[0]. This is because the old behavior would cause any plugin which was installed there to be enabled by default for *every* user on the system. This is a very unfriendly default, especially with plugins like latex-suite which are very invasive. We removed /usr/share/vim/addons from the runtimepath and now suggest that the user installs vim-addons-manager and uses the vim-addons command to enable, for their user, the plugins they want to use. Use of vim-addons-manager isn't required as you can still add /usr/share/vim/addons to your runtimepath (not recommended) or manually copy/symlink the plugins' files into the appropriate part of your ~/.vim/ directory. James [0] - http://pkg-vim.alioth.debian.org/vim-policy.html/x112.html -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature