Adding --gemfile= selection as an argument to exec

lloeki commented 7 years ago

I was trying to fix this in a way that doesn't involve gruesome hacks and matryoshka wrappers by going something along this route (4.9). Here's what I found:

setting BUNDLE_GEMFILE=where/is/Gemfool and running bundle exec rubocop -c where/is/.rubocop.yml where/is/my/file.rb works but requires setting an env var which is impractical and cannot be done without side effects in some cases (e.g multiple projects open in a single vim instance)
cd'ing into where/is/my and running bundle exec rubocop file.rb works but requires changing the pwd which cannot be done without side effects in some cases (vim plugins don't like things like autochdir)
bundle install --gemfile=Gemfool is a thing when it can use BUNDLE_GEMFILE already, so “there's BUNDLE_GEMFILE, use that” doesn't seem to carry much weight
running env BUNDLE_GEMFILE=where/is/Gemfool bundle exec rubocop -c where/is/.rubocop.yml where/is/my/file.rb works but may be hard to set as a command without side effects (vim-syntastic) so why is there --gemfile= for install? Also, maybe unix/shell dependent?
bundle exec can already take an optional argument ([--keep-file-descriptors]) so it's not like it can't take more, so not accepting one more doesn't seem to carry much weight either