Installation

Configuration

~/.gemrc

You no longer need to modify ~/.gemrc,
just remove the old entry to be sure it works as expected.
If you need to use your own custom_shebang,
you can define it in ~/.gemrc to override the default:

custom_shebang: $env <your_custom_shebang_program>

./.noexec.yaml

Though you can let noexec do it's own thing and rely on looking up your binary via your Gemfile,
you can also specify which binaries you want included or excluded.
Create a .noexec.yaml file along side any Gemfiles you want to use.
Then, to enable (or disable) the usage of your particular binary into your bundle,
add an include or exclude section. For example:

exclude: [rake]

Or,

include: [haml]

Disabling executables

In case you know certain binaries should not use bundler you can define a list of this binaries:

exportNOEXEC_EXCLUDE="gist bluepill"

Put it into ~/.bashrc or other shell initialization file to make it persistent.

Problems?

IRC support:

If you do not get an answer relatively quickly,
be sure to leave your email address so someone can get back to you later.

How does this work (ruby_noexec_wrapper)

It modifies gem wrappers shebang to load ruby_noexec_wrapper.
Then, when you run gem binaries, it takes a look at your working directory,
and every directory above it until it can find a Gemfile.
If the executable you're running is present in your Gemfile,
it switches to using that Gemfile instead (via Bundle.setup).