fish-shell/tests/checks/disown-parent.fish

# RUN: env fish_test_helper=%fish_test_helper %fish %s
#REQUIRES: command -v %fish_test_helper

# Ensure that a job which attempts to disown itself does not explode.
# Here fish_test_helper is the process group leader; we attempt to disown
# its pid within a pipeline containing it.

function disowner
    read -l pid
    echo Disown $pid
    disown $pid
end
$fish_test_helper print_pid_then_sleep | disowner

# CHECK: Disown {{\d+}}
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: env fish_test_helper=%fish_test_helper %fish %s`
tests: Specifically #require fish_test_helper when needed 2024-12-26 13:30:09 +01:00			`#REQUIRES: command -v %fish_test_helper`
Add a tricky test to verify disowning an in-flight job There's some logic in fish to prevent blowing up when an under-construction job is disowned. Add a test for it. 2019-12-08 11:44:21 -08:00
			`# Ensure that a job which attempts to disown itself does not explode.`
			`# Here fish_test_helper is the process group leader; we attempt to disown`
			`# its pid within a pipeline containing it.`

			`function disowner`
			`read -l pid`
			`echo Disown $pid`
			`disown $pid`
			`end`
			`$fish_test_helper print_pid_then_sleep \| disowner`

			`# CHECK: Disown {{\d+}}`