summaryrefslogtreecommitdiff
path: root/Doc/Zsh
diff options
context:
space:
mode:
authorPeter Stephenson <pws@zsh.org>2017-07-04 09:40:45 +0100
committerPeter Stephenson <pws@zsh.org>2017-07-04 09:40:45 +0100
commita955065cda3dcaa80058520ba55dc0bf5c8d3f08 (patch)
tree943ee67f8b9141d65b5bcfacba9d84bf721681bc /Doc/Zsh
parentcdd9402224da17e90b674a135e0183291c3f38ec (diff)
downloadzsh-a955065cda3dcaa80058520ba55dc0bf5c8d3f08.tar.gz
zsh-a955065cda3dcaa80058520ba55dc0bf5c8d3f08.zip
Delay processing "disown" for superjob.
This is a job forked from the current shell when a job partly running from the current shell was suspended. When all associated processes started from the main shell are finished the job is continued and at this point the disown can complete.
Diffstat (limited to 'Doc/Zsh')
-rw-r--r--Doc/Zsh/jobs.yo6
1 files changed, 6 insertions, 0 deletions
diff --git a/Doc/Zsh/jobs.yo b/Doc/Zsh/jobs.yo
index 6262dd244..70559f2d8 100644
--- a/Doc/Zsh/jobs.yo
+++ b/Doc/Zsh/jobs.yo
@@ -49,6 +49,12 @@ in the parent shell. Thus the behaviour is different from the case
where the function was never suspended. Zsh is different from many
other shells in this regard.
+One additional side effect is that use of tt(disown) with a job
+created by suspending shell code in this fashion is delayed: the
+job can only be disowned once any process started from the parent
+shell has terminated. At that point, the disowned job disappears
+silently from the job list.
+
The same behaviour is found when the shell is executing code as the
right hand side of a pipeline or any complex shell construct such as
tt(if), tt(for), etc., in order that the entire block of code