On Sun, Feb 10, 2008 at 11:39:12AM +0000, Colin Watson wrote: > On Fri, Feb 08, 2008 at 11:56:17PM -0500, James Vega wrote: > > 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 addon's functionality to the user. Since > > halibut only ships syntax/halibut.vim, it could also simply document > > that the user can symlink the file to ~/.vim/syntax/halibut.vim. > > I can understand why plugins should be disabled system-wide, but surely > syntax highlighting should be available automatically once the package > is installed? After all, in the absence of filetype detection you have > to use ':setf halibut' to enable it. It seems absurd to me to make users > jump through an extra hoop.
Well, it's not possible to have part of the runtimepath directory strucutre sourced by default and other parts not. Having to symlink a file, a quite simple task and one-time cost, is much easier than trying to figure out why you suddenly have random strings being inserted into your document as you type (such as by having vim-latexsuite installed and automatically enabled). Considering that halibut makes no mention of Vim in its description and only provides the Enhances relationship, I'd actually expect to see a README.Debian with a quick blurb about the syntax file. This could easily be extended to inform the user of how to make it available to Vim. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
