On Fri, 2008-02-08 at 23:22 -0500, James Vega wrote: > Package: bicyclerepair > Version: 0.9.4-2 > Severity: minor > > The README.Debian and README.vim imply that this plugin is automatically > sourced by Vim. As of the 1:7.1-022+1 upload of Vim, > /usr/share/vim/addons is not included in Vim's runtimepath and therefore > not automatically used by Vim. The Vim Addon Policy[0] describes the > suggested ways for a Debian package to provide an addons functionality > to the user. Since bicyclerepair only ships ftplugin/python_bike.vim, > it could also simply document that the user can symlink the file to > ~/.vim/ftplugin/python_bike.vim as the current documentation is out of > date.
It seems a shame to have broken every single vim addon rather than simply providing a new directory tree for sourcing addons which *are* problematic. Most addons do not get in the users way and are entirely safe to have enabled when the package is installed. Can we please unbreak this in vim rather than in the addons? -Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part
