1. Fixed some lines which were wider than 78 characters.
2. Added a couple of more borders above all the sub-sections.
3. Moved about part above the TOC, seems unnecessary to have that as its
own section when it's so small. This also look more like a  default vim
help file.
4. Changed "NOTE:" into "Note that" because that is more like how it's
used in default vim files.
5. Changed some wording like "the plug-in manager" to "a
plug-in manager".
6. Moved a couple of *tag names* below their headings so it's like that
everywhere in the file.

- until we figure out how to manage it…

Helptags seems to fail if some of the path components it receives are
symlinks. So resolve the symlink when calling helptags.

Improve README formatting, fix links

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.

fix code formatting, fix grammar and capitalization, update links, and much more

make the doc/vundle.txt the same as README.md

Failures in :helptags commands for individual bundles were logged but
the error were not propagated to the installer.

Warn the user when a leading or trailing space is found in one the
bundle specs they have configured using the Bundle command.

Ignore .netrwhist" until rtp ordering is fixed

Because vundle modifies the directory that appears first in the rtp, some files that vim generates in the first directory in rtp end up in the vundle directory. This is a known issue in vundle but until it is resolved, ignore .netrwhhist when found in the vundle directory.

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.

Certain wildignore values prevented the various logs from being
viewable.

Fixes #249

Fix wiki links

Github's new way of handling relative links broke some of the
links in the readme file.

Seems to have broken with GitHub's relative link change https://github.com/blog/1395-relative-links-in-markup-files

**V**imb**undle** no longer rendering properly...

Fixes #217

Closes #206: alias `BundleUpdate` to `BundleInstall!`

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.

'BundleUpdate' is a more intuitive and explicit command, whereas 'BundleInstall!' isn't.

- causes #203

This reverts commit 1e140c9f6b.

- link to contributors

- not all versions of vim 7.2 support the extra argument for glob*(),
  only those compiled with patch 51

- make it append only (instead both append + prepend)
- which draws *_rm_a and *_add_a useless as &rtp order gets preserved
- benefits: simpler, faster, less code

Fix wget/win32 codepath for script searching.

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

Vundle can manage Vundle, when it cloned as git submodule

When vundle installed as git submodule, git create file '.git' instead of
directory '.git'.

And vundle cannot update by self :(

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

Changelog does not work on Windows

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

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.

- as before Helptags returned 'updated'

- addresses #162 issues

Create Changelog when performing BundleInstall!

If no errors exist, the status-line will inform users how to view the
Changelog after BundleUpdate! is completed.