tests/status.err

status: Invalid combination of options,
you cannot do both 'is-interactive' and 'is-login' in the same invocation
status: Invalid combination of options,
you cannot do both 'is-block' and 'is-interactive' in the same invocation
status: Invalid job control mode 'full1'
status: Invalid job control mode '1none'

####################
# Future Feature Flags

####################
# Ensure $status isn't reset before a function is executed
make `status` saner vis-a-vis arg parsing The `status` command currently silently allows incompatible flags (i.e., subcommands). Too, using flags to specify subcommands misleads the user into thinking they can specify multiple subcommands. We recently modified the `history` command to deprecate using flags for subcommands. This change does the same for the `status` command. Fixes #3509 2016-11-04 22:32:43 -07:00			`status: Invalid combination of options,`
			`you cannot do both 'is-interactive' and 'is-login' in the same invocation`
			`status: Invalid combination of options,`
			`you cannot do both 'is-block' and 'is-interactive' in the same invocation`
			`status: Invalid job control mode 'full1'`
			`status: Invalid job control mode '1none'`
Add status subcomannds: features and test-feature This teaches the status command to work with features. 'status features' will show a table listing all known features and whether they are currently on or off. `status test-feature` will test an individual feature, setting the exit status to 0 if the feature is on, 1 if off, 2 if unknown. 2018-04-24 14:02:15 -07:00
			`####################`
			`# Future Feature Flags`
Test: validate $status is preserved on calling into a function 2019-04-13 12:11:42 -05:00
			`####################`
			`# Ensure $status isn't reset before a function is executed`