#!/bin/bash
eho -e "${bkwhite}\\n\\n LALAj ${bld}${red}%@. \\n bybyby @@@.\\n${bkwhite}"
Passing. With a command failure 'eho'! On this case a 'echo' mistaken command
'eho' command not exist!
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!
Most helpful comment
It is not practical to take every unknown, non-keyword, non-variable token and alarm on it.
ehocould 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.