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

Fix caps and highlight examples

John Gardner
2021-12-22 18:27:12 +11:00
parent 6e9b4c5248
commit 06aab0caab
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
SC1010.md

@@ -4,24 +4,24 @@
### Problematic code: ### Problematic code:
``` ```sh
for f in *; do echo "$f" done for f in *; do echo "$f" done
``` ```
or or
``` ```sh
echo $f is done echo $f is done
``` ```
### Correct code: ### Correct code:
``` ```sh
for f in *; do echo "$f"; done for f in *; do echo "$f"; done
``` ```
or or
``` ```sh
echo "$f is done" echo "$f is done"
``` ```
@@ -34,4 +34,4 @@ In the example, `echo "$f" done` is the same as `echo "$f" "done"`, and the `don
### Exceptions ### Exceptions
If you're intentionally using `done` as a literal, you can quote it to make this clear to shellcheck (and also human readers), e.g. instead of `echo Task is done`, use `echo "Task is done"`. This makes no difference to the shell, but it will silence this warning. If you're intentionally using `done` as a literal, you can quote it to make this clear to ShellCheck (and also human readers), e.g. instead of `echo Task is done`, use `echo "Task is done"`. This makes no difference to the shell, but it will silence this warning.