2019-08-08 17:30:28 +0100, Geoff Clare:
> Stephane Chazelas wrote, on 08 Aug 2019:
> >
> > 2019-08-08 15:39:18 +0100, Geoff Clare:
> > []
> > > I have repeated it with /bin/sleep instead of sleep. It still treated the
> > > whole AND-OR list as one job:
> > >
> > > $ { /bin/sleep 3 | /bin/sl
Stephane Chazelas wrote, on 08 Aug 2019:
>
> 2019-08-08 15:39:18 +0100, Geoff Clare:
> []
> > I have repeated it with /bin/sleep instead of sleep. It still treated the
> > whole AND-OR list as one job:
> >
> > $ { /bin/sleep 3 | /bin/sleep 4; /bin/sleep 1 | /bin/sleep 2; } && {
> > /bin/sle
2019-08-08 15:39:18 +0100, Geoff Clare:
[]
> I have repeated it with /bin/sleep instead of sleep. It still treated the
> whole AND-OR list as one job:
>
> $ { /bin/sleep 3 | /bin/sleep 4; /bin/sleep 1 | /bin/sleep 2; } && {
> /bin/sleep 5; /bin/sleep 6; }
> ^Z[1] + Stopped {
Stephane Chazelas wrote, on 08 Aug 2019:
>
> 2019-08-08 11:43:53 +0100, Geoff Clare:
> [...]
> > I tested a complex (although not as complex as yours) AND-OR list in
> > ksh93 and it treated the whole thing as one job:
> >
> > $ { sleep 3 | sleep 4; sleep 1 | sleep 2; } && { sleep 5; sleep 6; }
>
2019-08-08 11:43:53 +0100, Geoff Clare:
[...]
> I tested a complex (although not as complex as yours) AND-OR list in
> ksh93 and it treated the whole thing as one job:
>
> $ { sleep 3 | sleep 4; sleep 1 | sleep 2; } && { sleep 5; sleep 6; }
> ^Z[1] + Stopped { sleep 3 | sleep 4; s
Stephane Chazelas wrote, on 08 Aug 2019:
>
> 2019-08-08 10:21:14 +0100, Geoff Clare:
> [...]
> > A bigger issue with bg, in shells that treat each pipeline in a
> > foreground AND-OR list as a separate job, is that if one of those jobs
> > is stopped and then placed in the background, what happens
2019-08-08 10:21:14 +0100, Geoff Clare:
[...]
> A bigger issue with bg, in shells that treat each pipeline in a
> foreground AND-OR list as a separate job, is that if one of those jobs
> is stopped and then placed in the background, what happens to the
> remainder of the AND-OR list? For example:
Geoff Clare wrote:
> > sh
> > $ set -m
> > $ sleep 3 && sleep 4
> > ^Z
> > [1] + Gestoppt (Benutzer) sh
> >
> > Which is the Bourne Shell problem I mentioned: the whole shell stops.
> >
> > BTW: the underlying shell that reported the stopped shell is a bosh.
>
> This happened because yo
Robert Elz wrote, on 08 Aug 2019:
>
> | Who says those operations aren't supposed to change the results?
>
> Who says that they are, or are permitted to?
Paragraph 2 of bg description:
Using bg to place a job into the background shall cause its
process ID to become "known in the curr
A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=374
==
Reported By:eblake
Assigned To:ajosey
=
10 matches
Mail list logo
