cmd/help: usability tweaks.

- Don’t mention `brew home` or `brew options` as their output is in
  `brew info` (and the `(…|…)` is weird.
- Use full length flags for `-v` and `-d` to make more obvious what
  they are doing
- Don’t use `Developers`; instead point out it’s how you contribute
- Mention `brew commands` for `COMMAND` output (like we do with
  `FORMULA` and `brew search`)
- Point towards `docs.brew.sh`
This commit is contained in:
Mike McQuaid 2018-03-30 14:57:38 +01:00
parent cc2d9d926e
commit 4c07685258

View File

@ -1,7 +1,7 @@
HOMEBREW_HELP = <<~EOS.freeze
Example usage:
brew search [TEXT|/REGEX/]
brew (info|home|options) [FORMULA...]
brew info [FORMULA...]
brew install FORMULA...
brew update
brew upgrade [FORMULA...]
@ -11,17 +11,17 @@ HOMEBREW_HELP = <<~EOS.freeze
Troubleshooting:
brew config
brew doctor
brew install -vd FORMULA
brew install --verbose --debug FORMULA
Developers:
Contributing:
brew create [URL [--no-fetch]]
brew edit [FORMULA...]
https://docs.brew.sh/Formula-Cookbook
Further help:
man brew
brew commands
brew help [COMMAND]
brew home
man brew
https://docs.brew.sh
EOS
# NOTE Keep the lenth of vanilla --help less than 25 lines!