Fabian Boehm a6c36a014c Return a falsey status if the last -c command has a parse error ... This makes `fish -c begin` fail with a status of 127 - it already printed a syntax error so that was weird. (127 was the status for syntax errors when piping to fish, so we stay consistent with that) We allow multiple `-c` commands, and this will return the regular status if the last `-c` succeeded. This is fundamentally an extremely weird situation but this is the simple targeted fix - we did nothing, unsuccessfully, so we should fail. Things to consider in future: 1. Return something better than 127 - that's the status for "unknown command"! 2. Fail after a `-c` failed, potentially even checking all of them before executing the first? Fixes #9888		2023-07-12 18:06:34 +02:00
..
checks	Return a falsey status if the last -c command has a parse error	2023-07-12 18:06:34 +02:00
pexpects	share/config.fish: Quit if job expansion hack errors	2023-06-10 15:36:36 +02:00
test_functions	[tests] Increase tmux-sleep duration when not under CI	2022-09-16 18:26:49 -05:00
.gitignore
history_sample_bash	Support $(cmd) command substitution as alternative to (cmd)	2021-07-13 21:33:42 +02:00
history_sample_corrupt1
history_sample_fish_1_x	Enforce that history items must end with trailing newlines	2021-05-10 14:23:07 -07:00
history_sample_fish_2_0	Enforce that history items must end with trailing newlines	2021-05-10 14:23:07 -07:00
interactive.config	Remove some unused functions from the test harness	2020-11-15 09:17:23 +01:00
interactive.fish	Only retry failed pexpect tests under CI	2022-10-25 13:40:21 -05:00
test_driver.sh	fix build when path has spaces in it.	2021-10-22 02:27:19 -07:00
test_env.sh	tests/test_env.sh: fix copy paste error so we export XDG_RUNTIME_DIR	2021-10-23 18:59:15 +02:00
test_util.fish	Run each test fully independently in own environment	2021-08-29 08:56:12 +02:00
test.fish	cmake: Force color in the tests	2021-08-30 17:16:19 +02:00