Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Suggesting typos in 'bundle open foo' #2050

merged 0 commits into from

3 participants


This is more like an RFC than a genuine pull request, but anyway:

I use 'bundle open' a ridiculous number of times each day, but can never remember whether it's thinking_sphinx or thinking-sphinx, delayed-job or delayed_job, and so on.

This commit crowbars some Levenshtein loving into cli.rb

$ bundle open thinking_sphinx
Could not find gem 'thinking_sphinx' in the current bundle.
Did you mean thinking-sphinx?
$ bundle open rke
Could not find gem 'rke' in the current bundle.
Did you mean one of rake, hike or ffi?
$ bundle open awss3  
Could not find gem 'awss3' in the current bundle.
Did you mean aws-s3?

But it does feel kinda messy and inconsistent - it doesn't work with "bundle update foo", for example, mostly because it doesn't fit so easily into the top-level CLI#update and it seems wrong to start putting stuff like this deeper into the library.

Any thoughts? Would you like to see something like this in Bundler, or is it better off waiting for the fabled plugin architecture?


This pull request passes (merged 3d744bea into 3a1121a).


This pull request fails (merged 0b47ff87 into 3a1121a).


This pull request fails (merged 0eb1f83 into 3a1121a).


I'm not quite sure what that failing test (!/carlhuda/bundler/jobs/2081118/L455) is checking - is it important that 'bundle update foo' should both update 'foo', and install missing gems (rack) ?


Hm. Here's a second take on it : #2060

@jdelStrother jdelStrother merged commit 4d163e8 into from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Sorry, commit information is not available for this pull request.

Something went wrong with that request. Please try again.