In Windows, some users set the Cygwin shell as their Vim shell, make
Vundle consider this when deciding which flavour of commands to run when
cloning. Roughly check if the shell contains `sh` in it, and assume a
Unix shell, even when on Windows.
The wildignore setting affects the behaviour of the `= shorthand, so
this changeset replaces the last remaining use of such construct with a
call to exec.
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.
With just `git clone`, submodules are not grabbed. This is an issue for
certain plugins, such as 'kevinw/pyflakes-vim' that requires a pyflakes
submodule
Instead checking for specific text in the output of the git commands, determine
the status of the bundle by comparing the sha of HEAD before and after the
git pull command.
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.
- "transcient bundle" - a bundle installed with :BundleInstall or interactively
without being declared in .vimrc
- treat them the as if they were configured
- so everything works the same
- ie before this change helptags weren't generated automatically
with `BundleInstall bundle` or with interactive mode
- it changes the way `:BundleClean` works, since it removes directories
that aren't bundles
- FIX: `:source .vimrc` to let `:BundleClean` remove transcient bundles
- closes#99
- 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
BundleInstall sources the current vimrc in order to reload all Bundles
in order to consider new Bundles that might have been added by the user
directly on their vimrc file. This, however, should not be Vundle's
responsibility, changes in vimrc should not be applied unless it is
re-sourced explicitly by the user.
This makes Vundle use the known list of Bundles for installation.
