El mar, 22 abr 2008, Michael Homer escribió: > 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?
Usually vim scripts are tarballs (or vimballs) which are installed under $HOME/.vim hierarchy, but you could install then under $VIMRUNTIME anyway (allowing the addon being accesible to everyone). I think the general way is to install them under $HOME/.vim because each user choose his own addons. And usually to install an addon you only need to copy some files under a special hierarchy in $HOME/.vim (sometimes are required other places, but that's not usual). The perfect scenario will be if every addon could be installed system wide and it could be activated editing ~/.vimrc, but most addons are active when installed and to disable them you will need to read how the addon works. > 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. Well, recipes are not mandatory of course, but imho having them will allow anyone to add (and test) new addons for vim easily and fast, the user wont need to search the addon on internet. download and install it, Compile could do that. The idea is that vim addons aren't installed as system wide, really when installing a vim addon you only install it, by default is not active, each user could active/deactive the addon if he wants (copying files under his home directory). The VimAddonsManager can be saw as a tool to sync the Vim-* addons programs for each user. > 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? Well i asked in #vim how addons were managed in other distros and a debian developer explained me this method, they are doing the same, they install each addon under some tree hierarchy (not in the vim path) and with a ruby script they activate them and so on. Maybe i'm wrong and is not a good idea to have vim addons as recipes, or maybe is better to create them system wide and letting the user to know how to disable it, dunno, that's why i send the post before to commit anything. Aitor. -- If the kids are united they will never be divided! _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
