GitLab

This adds support for ForkLift 3, which uses a different
application id and also uses a popover instead of a sheet for
entering the directory to go to.

This also improves the handling of different versions of ForkLift,
by first choosing any currently running instance, and if none is
running starting the newest available version.

Fixes #6565.

This means that if you have, for example, `alias rs='rails server'`, you can
run `be rs` and have it expanded to `bundle exec rails server`.

Fixes #5818

* use https everywhere

* use https links on the files that are left

Also, removed some broken links and updated redirections.

* Add function to search Dash

* Pass all arguements instead of just the first

* Adding docset completion with help from @kapeli and [arx]

* Modifies the search logic for asdf to include Homebrew when it is
installed. The implementation is adapted from the pyenv plugin.

Fixes #6157

Fixes #7041

- Consolidates the switch-adding logic for readability.
- Replaces "[[ ... ]] && ..." with "if [[ ... ]]; then ..." in some
  cases to avoid a spurious nonzero exit status from _zsh_tmux_plugin_run.
- Puts error message on stderr instead of stdout

Also changes the tmux detection test to do an early exit if tmux is absent,
to reduce the indentation level of the main body of code.

When a commit has multiple tags associated to it, the git-prompt will
throw the following error:

git_super_status:[:4: integer expression expected: v0.21.x\ntags/v0.21.5,
git_super_status:[:7: integer expression expected: origin/v0.21.x,
git_super_status:[:11: integer expression expected: origin/v0.21.x,
git_super_status:[:14: integer expression expected: v0.21.x
git_super_status:[:23: integer expression expected: v0.21.x

This is due to the prompt expecting the tag field to be a single word
with no spaces in between but if there are multiple tags the python
script returns a string with ', ' space separated list of tags.
This throws off the parser. The solution is to ensure that the python
script returns a space-less string ensuring the git-prompt parser to
properly parse the data.
Signed-off-by: Thanh Ha <zxiiro@linux.com>

This updates the git-flow-avh plugin to the latest version
from https://github.com/petervanderdoes/git-flow-completion
(0.6.0 at the time of this commit).

This mainly adds support for the "git flow bugfix" command.

This PR replaces #4626 as well as #4705, both of which adds support for the bugfix command but doesn't use the official version from https://github.com/petervanderdoes/git-flow-completion

Fixes #4705
Fixes #4626
Fixes #5903

It seems that `bundle version` calls git to know the commit sha, while `bundle --version` only shows the version of bundler.

Fixes #6988

Fixes #5722
Fixes #5864
Fixes #5920
Fixes #6566
Fixes #6579
Fixes #6686
Fixes #6740

Version: ff73f40 (2018-05-02)

Fixes #5859
Fixes #5878
Fixes #5983
Fixes #6013

* Fix dotenv plugin accepted file format

* clarify README and add disclaimer section

* Add Yarn upgrade-ineractive CLI command

* Remove dots at the end of completions

This can avoid big mistakes as this I just made.
I thought I could give it an argument. So, now, it is possible.

Fixes #5874

Related:
https://github.com/lukechilds/zsh-nvm/issues/23
https://github.com/zsh-users/antigen/issues/586

* add plugin:percol

* fix format

* check percol

* fix empty history in gnome terminal

* Added magic-enter plugin

To bind commonly used tasks to the enter key

* Allow the magic-enter commands to be modified by the user

When invoking a shell as root using ```sudo -s```, the ssh-agent plugin
starts a new agent although it already exists.

The problem boils down to a check if ssh-agent is running using
```ps x```. If that is extended to ```ps ax``` for root, then the
existing ssh-agent will still work.