Shellcheck: Invalid command not noticed! bad 'eho' right echo

Created on 3 May 2020  路  3Comments  路  Source: koalaman/shellcheck

#!/bin/bash
eho -e "${bkwhite}\\n\\n          LALAj      ${bld}${red}%@. \\n      bybyby                @@@.\\n${bkwhite}"

Here's what shellcheck currently says:

Passing. With a command failure 'eho'! On this case a 'echo' mistaken command

Here's what I wanted or expected to see:

'eho' command not exist!

Most helpful comment

It is not practical to take every unknown, non-keyword, non-variable token and alarm on it. eho could be a program/function that will exist on whatever machine to which the script is installed, but not exist on the machine where shellcheck is run as part of a Continuous Integration setup, as one example.

All 3 comments

It is not practical to take every unknown, non-keyword, non-variable token and alarm on it. eho could be a program/function that will exist on whatever machine to which the script is installed, but not exist on the machine where shellcheck is run as part of a Continuous Integration setup, as one example.

There are unfortunately too many known and custom tools to keep track of, and too many names that are a single character away from other existing names (ss, ssh, pssh, rssh), so the false positive rate makes this check unfeasible in the general case.

You have all the reason!!! Thank you!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

erichelgeson picture erichelgeson  路  5Comments

arth1 picture arth1  路  4Comments

sobolevn picture sobolevn  路  4Comments

bje- picture bje-  路  3Comments

helau picture helau  路  4Comments