You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to generate warning for undefined command / function? The use case is to catch typos. In practice, I'm okay to maintain a dictionary of command / function names.
Here's a snippet or screenshot that shows the problem:
#!/bin/bash
echa "hello world"
Here's what shellcheck currently says:
No issues detected!
Here's what I wanted or expected to see:
Unknown command "echa"
The text was updated successfully, but these errors were encountered:
functicons
changed the title
Catch undefined command / function
Catch undefined commands / functions
Sep 14, 2022
I would highly vote for - Indicating misspelled functions/shell commands.
However, searching executable paths may be time consuming.
Furthermore, it will also yield false positives when the dev-environment is not the target machine.
Therefore I think that searching for misspelled commands/functions should not be the default.
It should be activated by a command line option.
For new checks and feature suggestions
Is it possible to generate warning for undefined command / function? The use case is to catch typos. In practice, I'm okay to maintain a dictionary of command / function names.
Here's a snippet or screenshot that shows the problem:
Here's what shellcheck currently says:
No issues detected!
Here's what I wanted or expected to see:
Unknown command "echa"
The text was updated successfully, but these errors were encountered: