Excerpts from Israel Chauca F.'s message of Fri Mar 25 00:35:56 +0100 2011: > That looks a bit convoluted to me, maybe because I'm not sure I got the idea.
Final result: system wide setup (or other user): /usr/vim-plugins/snipmate your setup (vam-default): ~/vim-addons/snipmate -> /usr/vim-plugins/snipmate (symlink) And you use the plugin managed by someone else. (But you told me you know how to use symlinks. They work perfectly within VAM managed directories as well - however keep in mind that updating all plugins may update this symlinked directory if its a VCS dir) About deactivation: Keep in mind that VAM also pays attention to dependencies. Eg if you use vim-addon-fcsh it will automatically load tlib. So removing tlib from the list passed to ActivateAddons will have (almost) no effect. > Usually, while troubleshooting. I don't like renaming or moving > directories from the terminal, I usually end up with a mess. So, > having a way to not load a plugin from vim is a nice thing to have for > me. There are two ways: a) disable a plugin, restart Vim, ... b) load without plugins, :ActivateAddons piecewise until the misbehaviour occurs. I usually copy paste the ActivateAddons() line: " call vam#ActivateAddons(["a","b"]) call vam#ActivateAddons(["a","b"]) then drop plugins from the second list. When done I know what to remove from the commented line. Probably this is a matter of taste only. It looks like we can stop this discussion. You have a solution. If you think that keeping your own fork is no longer worth it then you're welcome to join the VAM team :) Marc Weber -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
