| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
issue where Bundler.setup used up insane amounts of RAM and never returned.
|
|
|
| |
Previously, bundler would raise an error like "Could not find gem 'foo' in any of the gem sources", which was misleading and confusing. This closes #434.
|
| |
|
|
|
|
| |
put in the associated gems
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #408
|
|
|
|
| |
when running bundle exec
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
editor priority:
- $BUNDLER_EDITOR
- $VISUAL
- $EDITOR
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
guard by the password prompt and perhaps assume it is asking for a remote server's ssh password.
|
| |
|
|
|
|
| |
warning in the case of conflicted activations
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
with the Gemfile
|
| |
|
| |
|
| |
|
| |
|