# Explicitly source git flow completion (if it exists)

set -e

completion="$(brew --prefix)/share/zsh/site-functions/git-flow-completion.zsh"

if test -f $completion
then
  source $completion
fi

# Ignore FETCH_HEAD on completion
zstyle ':completion:*:*' ignored-patterns '*FETCH_HEAD'

# Explicitly source git flow completion (if it exists)

completion="$(brew --prefix)/share/zsh/site-functions/git-flow-completion.zsh"

if test -f $completion
then
  source $completion
fi

# Ignore FETCH_HEAD on completion
zstyle ':completion:*:*' ignored-patterns '*FETCH_HEAD'

Fix bug when "set -e" affects interactive shell commands
Fix bug when "set -e" affects interactive shell commands

Very nasty bug. It seems in some zsh version this behavior
was changed, at least I did not experience this before.

This "set -e" flag (propagates "fail fast" behavior, i.e.
when command fails it makes all script fail) somehow was
applied globally, that caused every non-successful command
that I typed to explode the whole shell.

So, rule of thumb: do not use "set -e" in shell scripts that
get sourced into your shell.
