Plugin requires files to be placed under "vimcurrent" directory

James Vega jamessan at debian.org
Sat Sep 17 17:46:16 UTC 2011


On Fri, Sep 09, 2011 at 04:07:55PM +0530, harish badrinath wrote:
> On Mon, Sep 5, 2011 at 2:46 AM, James Vega <jamessan at debian.org> wrote:
> > On Sun, Sep 04, 2011 at 01:19:52PM +0530, harish badrinath wrote:
> 
> 
> >> The plugin source tree contains a directory called autoload, when the
> >> contents of this directory are place in
> >> /usr/share/vim/vimcurrent/autoload, the plugin is functional.
> >> Else
> >> i get the following error
> >> "E117:Unknownfunction:conque_term#open"
> >
> > You'll likely find the Vim addon policy[0] useful.
> >
> 
> > Install your package's files to a directory specific to your package[1].
> > Since you're packaging the conque plugin, /usr/share/vim-conque may be a
> > logical place.  As an example, the autoload/conque_term.vim file could
> > be installed to /usr/share/vim-conque/autoload/conque_term.vim.
> 
> It worked. (Its not accepted into debian repo's as of today *yet*)
> I place the contents of autoload under /usr/share/vim/addons/.
> My computer did not have a autoload directory under "/usr/share/vim/addons/",
> so i asked this question.

As described in the policy, that's intentional.  One has to explicitly
enable an addon.  That's one of the things I plan on changing when the
next major version of vim-addon-manager and vim-policy are released.
The sysadmin should be able to indicate that they want addons enabled by
default.

> I noticed that if i place files under /var/lib/vim/addons/,
> even if the yaml file contains a "disabledby" field, the plugin is enabled
> by default. Is this a valid observation ??

Just because the yaml file contains the "disabled" field doesn't mean
that the plugin won't be loaded.

The user has to run “vim-addons disable addon-name”, which will put a
file in ~/.vim/plugin with the line specified in the "disabledby" field.
That line lets a variable which the plugin, when it is loaded, checks to
determine whether it is actually supposed to provide its functionality.

-- 
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jamessan at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20110917/05b794e6/attachment.pgp>


More information about the pkg-vim-maintainers mailing list