buffers will not persist after they're closed.

All global variables that are not part of the public API (mentioned in the
documentation) are turned into autoload variables.  This is intended to give
all global variables defined by Vundle.vim a common prefix.  The variable
g:default_git_proto is part of the public API and is therefor not changed.
This is the only exception.

Changed:
   g:bundle_dir            -> vundle#bundle_dir
   g:bundles               -> vundle#bundles
   g:updated_bundles       -> vundle#updated_bundles
   g:vundle_lazy_load      -> vundle#lazy_load
   g:vundle_log            -> vundle#log
Unchanged:
   g:default_git_proto

If it was loaded, unload the log buffer before editing it.  Otherwise the
editing command can "hang" if the user has `set hidden`.

This problem was originally discovered with the VundleChangelog command and
the analogous fix was applied in 7d9b10.  See github issue #468 for more.

These variables only occur in one file each.  By making them script local
variables this is "documented" in the code.  At the same time the global
namespace is polluted less.

Changed:
    g:bundle_names          -> s:bundle_names
    g:vundle_last_status    -> s:last_status
    g:vundle_log_file       -> s:log_file
    g:vundle_view           -> s:view

The command `silent pedit ...` was causing trouble if the user had `set
hidden`.  Now we `bdelete` the changelog buffer before editing it anew.

The previous method for interacting with a bundle via git involved
cd'ing into the bundle directory then running the relevant git commands.
The problem with this approach is that if the environmental variables
`GIT_DIR` and `GIT_WORK_TREE` are set at this point then git will
preference their values over those implied by the current directory.
(This can cause trouble for vcsh users, for example.)

This patch uses the git arguments `-C`, `--git-dir`, and `--work-tree`
to specify the location of the bundle explicitly. This overcomes the
original problem since git gives these values precedence over `GIT_DIR`
and `GIT_WORK_TREE`.

* Add modelines to all code/doc files excluding README.md.  The modeline used is: `" vim: set expandtab sts=2 ts=2 sw=2 tw=78 norl:`
* Rename links with /vundle to /Vundle.vim, seems to confuse some people with redirect.
* Remove duplicates from Quickstart, add example of `name` flag.
* Add link to Tips page by @Lucc .
* Change help maintain vundle link directly to the new one.
* README.md line number links updated.

Note: Users with bundle/vundle need to rename vundle to Vundle.vim to use test files. Vundle will continue to function otherwise.

Fixes #413.
Fixes #438.

- Complete the code documentation effort started by @lucc
- Remove some judgemental comments ✨
- Remove comments pertaining to things that should be opened as issues
- Boxed ❗

Also add some FIXME markers in places where the code needs more
explanation.

Still keep :Bundle backwards compatible.

- closes many issues )

Should fix #231.

Certain wildignore values prevented the various logs from being
viewable.

Fixes #249

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.

The codepath does not appear to have been tested; mv on Win32 is move,
and substitute has 4 arguments instead of 3.

- add /d switch to cd command to perform drive change
- enclose joined commands with quotes

Instead of creating a vundle_update tag to compare changes between update
and HEAD we now use the output from `git pull` to get initial/updated shas.

Distinction between `new` and `updated` simplifies the process
of adding a bundle to the updated_bundle list.

If the Bundle is hosted on GitHub include link to compare the commit range
visually on GitHub.

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.

- closes #64

- closes #110

Prevents the user from having to type a space before the search term.

- closes #80

- use `redraw` instead `redraw!`
- closes #90

- to avoid accidental removal

- so it better reflects the content

- do not clutter up ~/

- not sure if there's a need for log file in predefined location
- installer is verbose enough to signal errors

- to avod error when deleting nonexisting buffer

- 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

- merge with view()
- no need for having both

- 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

- TODO: refactor: extract common code

- Bundles is not a good name for search
- BundleSearch undeprecated
- TODO: repurpose :Bundles cmd