While trying to be smart about whether the requested executable is actually part of the Gemfile was a nice idea, in practice it didn’t work out:
Gems may include executables with names different than the name of the gem itself. Most prominent example: the rspec executable is provided by the gem rspec-core (for the record: this was causing rspec/rspec.tmbundle#111).
So from now an let’s just assume that if a project has a Gemfile, any executable should be run via bundle exec …. If needed, this behaviour can still be changed on a per-project basis by providing a custom binstub or setting TM_$EXECUTABLE appropriately.
While trying to be smart about whether the requested executable is actually part of the Gemfile was a nice idea, in practice it didn’t work out:
Gems may include executables with names different than the name of the gem itself. Most prominent example: the
rspec
executable is provided by the gemrspec-core
(for the record: this was causing rspec/rspec.tmbundle#111).So from now an let’s just assume that if a project has a Gemfile, any executable should be run via
bundle exec …
. If needed, this behaviour can still be changed on a per-project basis by providing a custom binstub or settingTM_$EXECUTABLE
appropriately.Fixes #120.