Don't prepend ./ to bundle exec argument? #8930
Description
With these two executable files:
> cat script.rb
#!/usr/bin/env ./runner
puts "Hello World"
> cat runner
#!/usr/bin/env ruby
puts ARGV.inspect
Executing bundle exec ...:
> bundle exec script.rb
["./script.rb"]
> bundle exec ./script.rb
["././script.rb"]
The former looks incorrect, e.g. bare:
> script.rb
fish: Unknown command: script.rb
it fails because it's missing ./.
And with ./, it gets an EXTRA ./ prepended, making the path unexpectedly ugly.
Of course, bundle exec is free to interpret the arguments how it sees fit, but double appending ./ is the worst possible outcome.