fish-shell/tests/checks/not.fish

#RUN: %fish %s | %filter-ctrlseqs

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
Extended & human-friendly keys See the changelog additions for user-visible changes. Since we enable/disable terminal protocols whenever we pass terminal ownership, tests can no longer run in parallel on the same terminal. For the same reason, readline shortcuts in the gdb REPL will not work anymore. As a remedy, use gdbserver, or lobby for CSI u support in libreadline. Add sleep to some tests, otherwise they fall (both in CI and locally). There are two weird failures on FreeBSD remaining, disable them for now https://github.com/fish-shell/fish-shell/pull/10359/checks?check_run_id=23330096362 Design and implementation borrows heavily from Kakoune. In future, we should try to implement more of the kitty progressive enhancements. Closes #10359 2024-03-30 16:10:12 +01:00			`#RUN: %fish %s \| %filter-ctrlseqs`
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 16:38:53 +01: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`