~emersion/mrsh-dev

Re: Issues with job control and nested shell processes

Details
Message ID
<NPVvRAcfVoAj-N7LiNAP0QITIxkLq8A148fhC3NJBxNpk13gOC5G4S0QkHNQOiefEfwXwVRBZvT2MxTSfR3lcFbm8cK5h8paWeoDUXzALQ0=@emersion.fr>
Sender timestamp
1559759072
DKIM signature
pass
Download raw message
On Wednesday, June 5, 2019 9:20 PM, Drew DeVault <sir@cmpwn.com> wrote:
> On Wed Jun 5, 2019 at 6:19 PM Simon Ser wrote:
>
> > The signal will be delivered to the mrsh process group. The child
> > processes are part of the same process group. mrsh will ignore the
> > signal, but child processes still receive it.
>
> Hm. Okay, but I don't like it.

Well, it's the only way to handle the general case.

> > > dash doesn't spawn a subshell in these cases, either :<
> >
> > It does seem to do it like mrsh:
> > $ sleep 999 && sleep 999 &
>
> I think it does with &&, where it needs a process to intepret the result
> of the first command, but with | it doesn't have its own shell process.

Indeed. That sounds like a reasonable optimization.