When calling `bundle install` with `--jobs=<n>`, bundle persists this
argument in `.bundle/config`. If we run `BUNDLE_JOBS=<n> bundle install`
instead, this is not persisted.

Fixes #10425

Co-authored-by: Marc Cornellà <marc.cornella@live.com>

Fixes #8892

* Change project URL from robbyrussell to ohmyzsh org

* Update git remote to use ohmyzsh org repository

When another function calls one of the bundler plugin's wrapper functions, the
command to run gets passed as an array instead of a space-separated string. That
works fine when the arguments are expanded alone, like `bundle exec $@`, but
something like `./bin/$@` will expand to something like `./bin/rake
./bin/--silent ./bin/--tasks`, which of course will explode. This was causing a
nasty interaction with the rake-fast plugin, and I'd be shocked if it wasn't
causing other problems.

The fix is to explicitly turn off the `RC_EXPAND_PARAM` option for that expansion.
See http://zsh.sourceforge.net/Doc/Release/Expansion.html#Parameter-Expansion
for more details.

The white space is causing an error and bundler cannot find any commands!

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

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

Fixes #6988

Use the same scheme as Darwin - sysctl instead of nproc, which doesn't exist in FreeBSD

Closes #2545
Co-authored-by: Daniel Bye <dbye@users.noreply.github.com>

Calling awk is not necessary here, sysctl has the -n flag to print the value.
Signed-off-by: Clemens Gruber <clemensgru@gmail.com>

The $OSTYPE variable is set at ZSH compile time and can be safely used
to determine the OS of the system. e.g. darwin (os x)

fixes #2076

related to #1587
closes #2200
closes #2561

closes #1817

closes #1825

closes #2779

This makes adding, deleting and merging a lot easier.