Skip to content

base-bash launcher: unrecognized single-dash options silently fall through to a confusing "script not found" error #290

Description

@codeforester

Summary

bin/base-bash's option parsing has an explicit catch-all for unknown --* long options, but no equivalent for unknown -* short options.

Details

bin/base-bash:906-921 (main() case statement) has an explicit --*) branch that reports "Unknown launcher option", but no -*) branch. An unmatched single-dash argument like -x falls out of the case entirely and is treated as $1 = script path, producing "Script '-x' was not found" instead of a clear unknown-option error — even though the usage text (base_launcher_usage) implies short options like -h/-V are recognized.

Impact

Users who typo a short flag get a misleading "script not found" error instead of an actionable "unknown option" message.

Suggested fix

Add a -*) case mirroring the --*) branch (excluding the already-handled -h/-V).

Metadata

Metadata

Assignees

Labels

bugSomething is not working

Type

No type

Projects

Status
Triage

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions