Parse Arguments in Bash ¶

Environment Variables¶

export

unset

explainshell.com is a great place for learning shell.
Bash-it/bash-it is a great community driven Bash framework.
It is suggested that you avoid writing complicated Bash scripts. IPython is a much better alternative.
Do NOT use ; to delimit paths passed to a shell command because ; terminates shell commands. Use , to delimit paths if needed.
$(some_command) is preferred over some_command. For more details, please refer to http://mywiki.wooledge.org/BashFAQ/082.

Redirect stdout to the file output and stderr to another file error.
```
 command > output 2> error
```
Redirect stderr to stdout (&1), and then redirect stdout to the file output.
```
 command > output 2>&1
```
Redirect both stdout and stderr to the file output.
```
 command &> output
```
It seems to me that tee does not work well sometimes. Basically, I have a Python script calling shell comamnds using subprocess.call. The output of the shell commands cannot be captured by tee. However, redirection using > partially works. Output of git commands (invoked by subprocess.call) cannot be redirected correctly. Actually, it turned out to be that both > and tee only works on a file in the current directly. And even so, some output of the git command invoked by subprocess.call is not captured. I have no idea why that happens. Not sure whether this is a bug in Mac, the Bash shell or due to the fact that I mixed shell commands and the print function in Python.
If there are logging from difference resources (e.g., both shell comamnd via subprocess.call and the print function in Python) to the standard output, make sure you flush the console so that output/error redirection works as expected.