..sorry..
--- Forwarded from Steffen Nurpmeso ---
Date: Wed, 23 Oct 2024 00:39:14 +0200
Author: Steffen Nurpmeso
From: Steffen Nurpmeso
To: chet.ra...@case.edu
Subject: Re: 5.2.37: bg(1)ed job then only runs partially
Message-ID: <2024103914.Qg9LVo-4@steffen%sdaoden.eu>
Chet Ramey wrote in
On 10/21/24 4:23 PM, Zachary Santer wrote:
On Mon, Oct 21, 2024 at 11:50 AM Chet Ramey wrote:
On 10/21/24 12:15 AM, Zachary Santer wrote:
The nontrivial stuff I do is still being run by bash 4.2 at the
moment, and I'm not willing to give up procsubs.
Probably something to take up with your
On 10/22/24 3:34 AM, cirrus.mazurka...@icloud.com wrote:
The following produces a `bash: test: too many arguments` exception in `test`,
with exit status 2:
``` bash
v='>'
test -n "$v" -a yes '!=' no # bash: test: too many arguments
echo $? # 2
test -n '>' -a 1 -eq 1 # bash: test: too many argu
On 10/21/24 6:29 PM, Steffen Nurpmeso wrote:
Hello.
So first: this thread must not even start if the answer is "bash
justs sends a signal to the job's entire process group, if the
programs do not properly deal with that it cannot help that".
(ogg123 in particular is known to have signal issues.)
On Tue, Oct 22, 2024 at 03:34:43PM +0800, cirrus.mazurka...@icloud.com wrote:
> The following produces a `bash: test: too many arguments` exception in
> `test`, with exit status 2:
>
> ``` bash
> v='>'
> test -n "$v" -a yes '!=' no # bash: test: too many arguments
> echo $? # 2
>
> test -n '>' -
The following produces a `bash: test: too many arguments` exception in `test`,
with exit status 2:
``` bash
v='>'
test -n "$v" -a yes '!=' no # bash: test: too many arguments
echo $? # 2
test -n '>' -a 1 -eq 1 # bash: test: too many arguments
echo $? # 2
[ -n '>' -a 1 -eq 1 ] # bash: [: too man
