Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
"bundle" without any arguments is equivalent to "bundle install" #1452
It seems to be conventional that command line programs should execute, when called without arguments, only if they are nullipotent. For instance, the command
If a command line program is not nullipotent, then its default behaviour when called without arguments should be to behave as though it has been called together with its
If this is intended behaviour, then the intention is questionable insofar as it breaks the command line conventions I've outlined above, to little advantage (a terser way of calling
If you've already run
Changing this behaviour right now would be unhelpful for the users of Bundler who are familiar with it. Yes, it breaks command-line conventions, but I don't see any reason to change it now besides that.
Thanks for reviewing the bug, Ryan.
It sounds like you agree
Yet besides these rather compelling reasons, you see no cause to change the
However, given that the number of (potential) users of Bundler who are used
Surely the sooner this is fixed the smaller the number of inconvenienced
The nullipotent reason is a bit academic but probably correct. The more compelling reason is that since there are so many bundler commands, it's not completely obvious what it's behaviour is without arguments. I just had some beginners ask me what the difference is between 'bundle' and 'bundle install' and I never get this question with 'ls'