[gobolinux-devel] Vim Addons Recipes

[Michael Homer]

On Tue, Apr 22, 2008 at 3:28 AM, Aitor Pérez Iturri
<aitor.iturri at gmx.com> wrote:
> El lun, 21 abr 2008, Daniele Maccari escribió:
>  > Aitor Pérez Iturri wrote:
>  > >Hi all,
>  > >
>  > Hola :D
>  > Just my two cents, as always.
>  > >I'm planning to create some recipes for vim addons (scripts and so on),
>  > >but i don't like the idea of have them installed in system paths because
>  > >vim scripts are intended to be installed under the user home directory.
>  > >
>  > Are they supposed to be installed there for some particular reason?
>  > Otherwise I think we could well install them system wide.
>
> > As said above, having something installed under /Programs and then
>  > having also to provide a script (as little as it can be) to move things
>  > under the user's home directory sounds a bit of a hack to me, if not
>  > useless.
>  > What is the standard way suggested to install these addons?
>  >
>  > Daniele
>  Hola Daniele!
>
>  Well those scripts are supposed to be installed in the user home
>  directory, some scripts add functionalities that many users doesn't want
>  (changing for example how vim shows functions and so on), so my idea is
>  that the system admin install the plugins but each user activate the
>  addons he/she wants to use. I was talking with a debian developer in the
>  #vim channel and they use a similar method, but their vim addons
>  packages comes with a registry of files the addon include, we don't need
>  that registry because we have each package splittled from the rest.
>
>  The idea of install under "vimfiles" directory is only to know that the
>  recipe is a vim addon.
>
>  If you want we could support the addons system wide, so each addon
>  installed is loaded by vim (for all users) and the user needs to read
>  how the addon works to disable it if he wants.
Could you explain a little more how the addons system for vim works?
I'm a little uncomfortable managing files under ~; is the usual way to
install them just to copy the files into a directory and have them
automatically included, or to modify ~/.vimrc to include the file?

In the case where they are always installed under ~, are recipes for
them really necessary at all? Installing or upgrading them in the
system wouldn't have any effect.

As well, if there is a need for such a tool, it seems it shouldn't be
tied to a particular distribution if it doesn't have to be. It's a
generic task that everybody would have to deal with. Is there an
existing project somewhere to deal with it?
-Michael