diff options
| author | Matt Brictson <matt@mattbrictson.com> | 2015-07-21 14:31:51 -0700 |
|---|---|---|
| committer | Matt Brictson <matt@mattbrictson.com> | 2015-07-21 14:31:51 -0700 |
| commit | edff91d0d8feff7ed410490574513c214823d2c4 (patch) | |
| tree | cd89ee124c2c1763303991f68c4042add78ce50b /DEVELOPMENT.md | |
| parent | 1bc75e0b6748bd37dd92189e1f347abebcf78971 (diff) | |
| download | bundler-edff91d0d8feff7ed410490574513c214823d2c4.tar.gz | |
bin should be exe in `alias dbundle` instructions
Diffstat (limited to 'DEVELOPMENT.md')
| -rw-r--r-- | DEVELOPMENT.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 46b519d9..464dfec3 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -29,7 +29,7 @@ Bundler doesn't use a Gemfile to list development dependencies, because when we 3. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias: - $ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/bin/bundle' + $ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle' With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command. |