GitLab

Vagrant 1.6 introduced the `global-status` command which allows
to get a quick overview of all active Vagrant environments for the
currently logged in user.

Vagrant 1.5 added Vagrant Cloud to share boxes. Some boxes
may be protected, the `login` command allows to access those
protected boxes from Vagrant Cloud.

Vagrant 1.5 introduced Vagrant Share to allow remote access to a Vagrant
environment. This adds support for the `share` and `connect` commands.

Vagrant 1.6 introduces a couple new commands, including the `version` command.
The `version` command shows the currently installed version information and
also checks for new updates available.

This is exactly what happens on tab completion for docker rmi. This commit
fixes that.

```sh
$ docker rmi <hit TAB>
_arguments:comparguments:312: invalid argument: __docker_images
_arguments:comparguments:312: invalid argument: __docker_images
_arguments:comparguments:312: invalid argument: __docker_images
```

In Python3 without universal_newlines set to True
output from Popen was byte-encoded.

Spelling correction in itunes control function.

The mailcatcher gem does not work correctly when executed through Bundler.

adding urldecode_json to compliment urlencode_json and updating readme.md; slight tweak to urlencode_json from previous commit

Many deprecations since 0.8 and new commands.

This commit allows for paths with spaces to be symlinked
in Pow.

If an application is located in a folder like `/some path/to the/app`
the powit command would fail when it shouldn't. It's not the case
anymore.

Rendering the 'vagrant box (remove|repackage)' completion code independant of Vagrant implementation details.

Added an <esc> to the begining of everything. I ran something when I was in insert mode once and all it did was shove !args... into the buffer.  <esc> first.

Added an optional callout to the end of the interaction function. I put it in to allow me to put the window focus on MacVim / GVim depending on the different OS I happen to be on

Fixed: If you callvim on a non-existant file with a relative path, the CWD of the running gvim process is used, and that's not right.  We use the PWD explicitly instead, in this case