github
/
the-art-of-command-line
mirror of https://github.com/jlevy/the-art-of-command-line
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Added curly-braces-in-script hint 

Signed-off-by: Andreas Hofmann <mail@andreas-hofmann.org>
pull/429/head
Andreas Hofmann 2016-07-09 13:22:20 +02:00
parent 49918189ad
commit a2d687b2fc
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -145,6 +145,14 @@ Notes:
diff /etc/hosts <(ssh somehost cat /etc/hosts) diff /etc/hosts <(ssh somehost cat /etc/hosts)
``` ```
- When writing scripts you may want to put all of your code in curly braces:
```sh
{
# Your code here
}
```
If the closing brace is missing, your script will be prevented from executing due to a syntax error. This makes sense when your script is going to be downloaded from the web, since it prevents partially downloaded scripts from executing.
- Know about "here documents" in Bash, as in `cat <<EOF ...`. - Know about "here documents" in Bash, as in `cat <<EOF ...`.
- In Bash, redirect both standard output and standard error via: `some-command >logfile 2>&1` or `some-command &>logfile`. Often, to ensure a command does not leave an open file handle to standard input, tying it to the terminal you are in, it is also good practice to add `</dev/null`. - In Bash, redirect both standard output and standard error via: `some-command >logfile 2>&1` or `some-command &>logfile`. Often, to ensure a command does not leave an open file handle to standard input, tying it to the terminal you are in, it is also good practice to add `</dev/null`.