Update submodule vim/bundle/vim-addon-manager 2752807...449dfd5
Update submodule vim/bundle/vim-addon-manager 2752807...449dfd5

* vim/bundle/vim-addon-manager 2752807...449dfd5 (53):
  > Merge pull request #102 from samflores/master
  > Improved documentation: - Fixed section numbers - Moved 2.10. to 16.1. - Some other fixes (wording and typos)
  > document where to find plugins and how a plugin should look like
  > Source_missing_files hack already does not work with directories with comma. So remove escaping them.
  > Format command sections using >; rework 50 (now 17) section.
  > Put new error messages section to VAM-trouble-shooting.
  > Don’t encourage using eval() and exec, especially the first. Also work with commas. Fixes #100
  > add trouble shooting section so that people in the future get an idea about what is wrong
  > revert the empty(&rtp) boilerplate. The correct fix is to use fnameescape
  > keep ugly eval because its declarative and descriptive. is_installed is more descriptive than isdirectory
  > Merge commit '0b4b04ee0ce7274418a17bf3f49bf593672d26eb'
  > Fixed runtimepath escaping issues in SetupVAM() example function
  > Respect &loadplugins option.
  > Also call expand(fnameescape()) for additional_addon_dirs Ref #94
  > merge changes by ZyX and add some additional documentation
  > Fixed events list. Seem to work properly now.
  > Added automatical detection of what events in what groups should be called when plugin was activated at runtime Ref #95
  > Fix slashes in binary_utils option It is completely possible for “expand()” to return string with forward slashes on windows: it is done if &shellslash is true
  > Double-sourcing will be problematic if plugin_root_dir contains metacharacters Don’t expand environment variables, buffer names and all that stuff. In any case documentation doesn’t say it is supported
  > Remove check for directory with newline from completion With additional_addon_dirs code for checking for NLs in directory name seems too complex for that rare case
  > Make completion also use plugins from additional_root_dirs
  > Fixed documentation, it looked like if “additional_addon_dirs” set to true will enable pulling plugins from /usr/shared-plugins
  > Remove obsolete code (this is end of 2012)
  > adding multiple addon_dirs
  > Make completion function filter out non-directories Also make it always add variants in case vim is at least 7.3.465
  > document why using runtimepath yourself will make only most plugins work
  > Merge pull request #93 from yanick/typo
  > thanks to emma-dev this typo got caught
  > document why source_missing_files exist
  > With this regex 0 may succeed check, -1 will always fail
  > after/ directories were already added to the runtimepath so it makes no sense to glob them separately. Also fixed some other minor things.
  > Merge branch 'master' of ssh://github.com/MarcWeber/vim-addon-manager
  > Merged smp-fix. Fixes #92
  > Merge
  > Made test quit after it is done
  > Replaced all dict['alphanum_key'] with dict.alphanum_key
  > Added note about prefered YAML implementation
  > Added information about how to test VAM using test.zsh
  > Added a way to disable SourceMissingPlugins hack as it is not needed when calling ActivateAddons from the vimrc
  > Changed :function endings: :endfun instead of :endf/:endfu Changed :if endings: :endif always, no :end
  > Fixed bisect, it was not limiting activated plugins at all Added test for bisection (still needing plugins with dependencies bisection testing)
  > Fixed escaping (it was wrongly double-escaping % and !) Fixed throw message (wrong command names) Made *VAMBisect commands able to be chained with pipe
  > Using proper globs: ignoring &suffixes and &wildignore, escaping directory names
  > Fixed bisect
  > Merge remote-tracking branch 'origin'
  > Made all commands except AddonsBisect able to be chained with pipe
  > Improved bisection:   Improved bisect#StepBad:     1. there is $MYVIMRC variable, no need to have a big bunch of has() checks.     2. made it use proper ! escaping.   Fixed bisect#Bisect: seems nobody cared to test whether it actually accepts arguments   Improved bisect#Bisect: it now uses v:progname to determine vim executable name   Improved documentation: added a note about how the problem can be tested automatically
  > Moved bisection to autoload/vam/bisect.vim
  > add minimal .vimrc versions because the commented got that bloated
  > document AddonsBisect, rename VAMBisect to AddonsBisect
  > VAM: add simple bisect support
  > Merge
  > Some documentation improvements

scorpiovn/dotfiles,scorpiovn/dotfiles,blueyed/dotfiles,scorpiovn/dotfiles,blueyed/dotfiles,scorpiovn/dotfiles,blueyed/dotfiles,blueyed/dotfiles,scorpiovn/dotfiles,blueyed/dotfiles