2017-12-03 17:31:00 -0500, Chet Ramey:
> On 12/1/17 2:00 PM, Stephane Chazelas wrote:
>
> > Also, there's a lot of problems reported at
> > unix.stackexchange.com at least that are caused by bash not
> > waiting for the processes started by process substitutions,
> > especially the >(...) form.
>
On 12/1/17 2:00 PM, Stephane Chazelas wrote:
> Also, there's a lot of problems reported at
> unix.stackexchange.com at least that are caused by bash not
> waiting for the processes started by process substitutions,
> especially the >(...) form.
Bash always reaps these processes. Do you mean waiti
On 12/1/17 12:40 PM, d...@computer42.org wrote:
> Bash Version: 4.4
> Patch Level: 12
> Release Status: release
>
> Description:
> I'm sanitising urls from advertisement crap. As described below I'm getting
> a wrong resolution of parenthesised expression defined with non-greedy
> operator '?
On 11/29/17 5:36 PM, Tobias Hoffmann wrote:
> Description:
> As stated in the man page, bash will only allow a single coproc at a time.
> Thus, when a first coproc has already ended, a second one can be created.
> This can e.g. be verified by commenting out the upper #sleep line, below.
> Alternat
