fish-shell/tests/checks/not.fish

#RUN: %fish %s

not true
echo $status
# CHECK: 1

# Two "not" prefixes on a single job cancel each other out.
not not sh -c 'exit 34'
echo $status
# CHECK: 34
tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive. 2024-04-12 18:19:32 +08:00			`#RUN: %fish %s`
Declare that two "not" keywords cancel each other out "not not return 34" exits with 34, not 1. This behavior is pretty surprising but benign. I think it's very unlikely that anyone relies on the opposite behavior, because using two "not" decorators in one job is weird, and code that compares not's raw exit code is rare. The behavior doesn't match our docs, but it's not worth changing the docs because that would confuse newcomers. Add a test to cement the behavior and a comment to explain this is intentional. I considered adding the comment at parse_execution_context_t::populate_not_process where this behavior is implemented but the field defintion seems even better, because I expect programmers to read that first. Closes #8377 2021-12-28 23:38:53 +08:00
			`not true`
			`echo $status`
			`# CHECK: 1`

			`# Two "not" prefixes on a single job cancel each other out.`
			`not not sh -c 'exit 34'`
			`echo $status`
			`# CHECK: 34`