7x31/shellcheck
1
0
Fork 0
mirror of https://github.com/koalaman/shellcheck.git synced 2025-10-03 19:29:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated SC2015 (markdown)

Mingye Wang
2020-06-11 18:53:25 +08:00
parent 1545ecb380
commit 56fe9781b4
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
SC2015.md

@@ -31,14 +31,13 @@ If an `if` clause is used instead, this problem is avoided.
### Boring detail: ### Boring detail:
We can think of the example above as We can think of the example above as
```sh ```sh
((([[ $dryrun ]]) && echo "Would delete file") || rm file) ((([[ $dryrun ]]) && echo "Would delete file") || rm file)
``` ```
expressing the left-associativity of the `&&` `||` operators. expressing the left-associativity of the `&&` `||` operators.
Whenever a command (strictly, a pipeline) succeeds or fails, the execution proceeds following the next `&&` (for success) or `||` (for failure). Whenever a command (strictly, a pipeline) succeeds or fails, the execution proceeds following the next `&&` (for success) or `||` (for failure). (More strictly, the parentheses should be replaced with `{ command; }` to avoid making a subshell, but that's ugly and boring.)
### Exceptions ### Exceptions
Ignore this warning when you actually do intend to run C when either A or B fails. Ignore this warning when you actually do intend to run C when either A or B fails.