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

note an exception where warning is invalid

Todd Walton
2020-12-09 12:47:38 -05:00
parent fea2c6d069
commit d069913bd1
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
SC2210.md

@@ -29,6 +29,8 @@ This is not likely to be intentional. The most common causes are:
1. Trying similarly to compare command output, as in `grep -c foo file > 100` instead of `[ "$(grep -c foo file)" -gt 100 ]` 1. Trying similarly to compare command output, as in `grep -c foo file > 100` instead of `[ "$(grep -c foo file)" -gt 100 ]`
1. Malformed FD operations, such as writing `1>2` instead of `1>&2`. 1. Malformed FD operations, such as writing `1>2` instead of `1>&2`.
If you do want to create a file named `4`, you can quote it to silence shellcheck and make it more clear to humans that it's not supposed to be taken numerically.
### Exceptions: ### Exceptions:
None. If you do want to create a file named `4`, you can quote it to silence shellcheck and make it more clear to humans that it's not supposed to be taken numerically. If you use the `&>` form of redirection, as in `foo > /dev/null 2&>1`, it will trigger this warning. You can safely ignore this warning if that is what triggered it, or change your redirection operator to the semantically preferable `>&`.