diff options
| author | Markus Reiter | 2018-01-28 04:33:33 +0100 |
|---|---|---|
| committer | GitHub | 2018-01-28 04:33:33 +0100 |
| commit | 5244755a5283f72ec1684a9e4b44a6aed2d51a82 (patch) | |
| tree | 4afc12ad5d7c6f0e6302165fe7213453b76e3973 | |
| parent | 9b2610b0adc84db194c5e735f3b385ead5a96fd3 (diff) | |
| parent | d4a9ffee2f97ca4624e2fb8eeeff32cd241bd048 (diff) | |
| download | brew-5244755a5283f72ec1684a9e4b44a6aed2d51a82.tar.bz2 | |
Merge pull request #3741 from kant/patch-1
Minor proposal
| -rw-r--r-- | docs/External-Commands.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/External-Commands.md b/docs/External-Commands.md index 881a1293a..65282fcb1 100644 --- a/docs/External-Commands.md +++ b/docs/External-Commands.md @@ -16,7 +16,7 @@ In both cases, the command file should be executable (`chmod +x`) and live somew ### Ruby commands An external command `extcmd` implemented as a Ruby command should be named `brew-extcmd.rb`. The command is executed by doing a `require` on the full pathname. As the command is `require`d, it has full access to the Homebrew "environment", i.e. all global variables and modules that any internal command has access to. -The command may `Kernel.exit` with a status code if it needs to; if it doesn't explicitly exit then Homebrew will return 0. +The command may `Kernel.exit` with a status code if it needs to; if it doesn't explicitly exit then Homebrew will return `0`. ### Shell scripts A shell script for a command named `extcmd` should be named `brew-extcmd`. This file will be run via `exec` with some Homebrew variables set as environment variables, and passed any additional command-line arguments. |