eof is not on a separate line SH-1042
Found eof further down, but not on a separate line. Close matches include -eof (!= eof).
Whitespace detected between # and ! in the shebang SH-1115
The script has spaces between the # and ! in the shebang. This is not valid. Remove the spaces so the OS can correctly recognize the file as a script.
Deprecated $[..] used SH-2007
The $[..] syntax was deprecated in Bash 2.0 and replaced with the standard $((..)) syntax from Korn shell. It is therefore recommended to use $((..)) instead.
Consider using find instead of ls to better handle non-alphanumeric filenames SH-2012
Missing fi statement here SH-1047
Expected fi matching previously mentioned if statement.
Missing ! in shebang SH-1113
You appear to be specifying a shebang, but missing the bang (i.e. !). The shebang should always be of the form #!/path/shell.
Executing output of a command SH-2091
Remove surrounding $() to avoid executing output (or use eval if this is intentional).
Lexicographical comparison operator used for numerical comparison SH-2071
Syntax error SH-1070
There's a syntax error at the highlighted location. This will cause the shell to crash with a syntax error as well.
Single quote not escaped properly SH-1003
Problematic code:
Escape \< to prevent it redirecting (or switch to [[ .. ]]) SH-2073
Mismatched keyword SH-1089
This error is typically seen when there are too many fis, dones or esacs , or when there's a do or then without a corresponding while, for or if.
Empty then clause detected SH-1048
$ used on the left side of an assignment SH-1066
Unlike Perl or PHP, $ is not used when assigning to a variable.
Braces are required for positionals over 9 SH-1037
For legacy reasons, $10 is interpreted as the variable $1 followed by the literal string 0. Curly braces are needed to tell the shell that both digits are part of the parameter expansion.
Consider using $HOME instead of tilde ~ to expand in quotes SH-2088
Unicode single quote used SH-1016
Problematic code:
Whitespace detected after the here-doc end token SH-1118
The end token of your here document has trailing whitespace. This is invisible to the naked eye, but shells do not accept it.
Invalid or unescaped ( found SH-1036
The checker expected an ordinary shell word but found an opening parenthesis instead. Determine what you intended the parenthesis to do and rewrite accordingly. Common issues include: * Wanting them to be literal, as in echo (FAIL) Some tests failed. In this case, it requires quoting.
Invalid use of parentheses SH-1088
Parentheses are special characters in shell and must be used correctly. For commands that expect literal parentheses, such as grep or find, the parentheses need to be quoted or escaped so the shell does not interpret them, and instead passes them to the command.