* created autoload/vundle/compat.vim: "compatibility" module
(implements functions not available in previous vim versions);
(code taken from my previous commit in 'autoload/vundle/config.vim',
then modified and extended);
* added compatibility function for shellescape();
* autoload/vundle/config.vim: tidied up so that it's a bit closer to
the file upstream;
* (previous commit) but added a few performance improvements (avoid
unnecessary calls and/or operations);
* altered other scripts to use 'vundle#compat#*()' functions instead of
those not necessarily available in previous vim versions;
inspired by
https://github.com/gmarik/vundle/pull/228 and
https://github.com/gmarik/vundle/pull/172
Vim patch #445 changed shell escaping and introduced incompatabilities for vundle.
Now vundle only escapes joined commands with double quotes on windows when shellxquote is not set to '('.
This workaround closes https://github.com/gmarik/vundle/issues/146 - the mentioned workaround
is no longer needed, but it does not break a vim configurations which contains "set shellxquote=".
DRY shell escaping and modified (hopefully) all relevant places.
Keeps track of the current commit with a vundle_update tag before
perfoming an update and adds all commits pulled in the update to a
Changelog accessible via pressing 'u' after BundleInstall! completes.
- batch process just iterates through the lines and calls specified
action
- individual actions give visual feedback aswell
- allow Helptags command as a part of installation process
- log is global array so log can be viewed any time
- log gets written to a defined location ~/.vim-vundle/vundle.log
- TODO: write log changes as they happen