fish-shell/tests/checks/caller-exit.fish

#RUN: %fish %s | %filter-ctrlseqs
echo (function foo1 --on-job-exit caller; end; functions --handlers-type caller-exit | grep foo)
# CHECK: caller-exit foo1
echo (function foo2 --on-job-exit caller; end; functions --handlers-type process-exit | grep foo)
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 23:10:12 +08:00			`#RUN: %fish %s \| %filter-ctrlseqs`
functions: list caller-exit handlers correctly `functions --handlers-type caller-exit` did not list any functions, while `functions --handlers-type process-exit` listed both process-exit and caller-exit handlers: $ echo (function foo --on-job-exit caller; end; functions --handlers-type caller-exit \| grep foo) $ echo (function foo --on-job-exit caller; end; functions --handlers-type process-exit \| grep foo) caller-exit foo 2023-02-11 19:44:31 +08:00			`echo (function foo1 --on-job-exit caller; end; functions --handlers-type caller-exit \| grep foo)`
			`# CHECK: caller-exit foo1`
			`echo (function foo2 --on-job-exit caller; end; functions --handlers-type process-exit \| grep foo)`