Andrew

E.g., non-en-US, a common default interpreter encoding. Or even warn on non-ASCII content. Best to offer blocklists, allowlists for customization.

Offer a `-print0` option to emit results using a NULL 0x00 separator rather than a line terminator separator. This helps recursive commands like: ```sh stank . | xargs shellcheck ```...

Spaces in filenames present a tremendous, unnecessary burden on code manipulating these files. Everything from POSIX sh, to UNIX find, to xargs, makefiles, and tab completion gets screwy on spaces....

Modelines can help many text editors to better highlight scripts, reducing the need for users to configure their text editors. When file extensions / shebangs / mimetypes are insufficient or...

bash subset scripts should be relatively suitable for linting with bashate. We may want to distinguish between: * non-bash scripts (e.g. POSIX sh, ksh, csh, fish, etc.) * full bash...

Register dtksh interpreter, file extension as ksh family POSIXy language.

* Any signal with `EXIT` is redundant, * `EXIT` covers most of a user's needs.

* [ ] Establish a conventional "build" script as a basic build system for defining common dependent tasks. * [ ] Have a convention for declaring task names, that works...

Like UNIX find, stank should offer a flag to use a zero value byte terminator instead of a line break, in order to help with gnarly scripts with spaces in...

As an expect developer, I want stank to recognize expect scripts as distinct from POSIXy shell scripts, so that I do not apply shell linters to non-shell scripts. UNIX `expect`...