tests/checks/caller-exit.fish

#RUN: %fish %s
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)
tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive. 2024-04-12 12:19:32 +02:00			`#RUN: %fish %s`
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 12:44:31 +01: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)`