Thank you very much, will keep that in mind.
--
Sent from: http://gnu-bash.2382.n7.nabble.com/
Amazing! Thank you very much for the swift solution :)
Best regards,
Jonas
‐‐‐ Original Message ‐‐‐
On Monday, May 17, 2021 12:36 AM, Chet Ramey wrote:
> On 5/16/21 4:07 PM, Jonas Alfredsson wrote:
>
> > Hi Chet,
> > Thank you for the response.
> > If I read it correctly you agree that
return code 127 by not found cmd or job
.. ?
On Sun, May 16, 2021, 22:08 Jonas Alfredsson <
jonas.alfreds...@protonmail.com> wrote:
> Hi Robert,
>
> Thank you for your response.
>
> > Don't use non standard command extensions
> > in test scripts like this.
>
> Apologies, this is my first reported
Date:Mon, 17 May 2021 21:35:49 +0200
From:Alex fxmbsw7 Ratchev
Message-ID:
| return code 127 by not found cmd or job
| .. ?
Yes, we always knew that, that was never interesting. The question
was why it was happening when the job still existed.
Chet has supp
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
-DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin'
-DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/ba
Nevermind! I was misunderstanding what the 'command' builtin does!
Thank you,
Carl
> On 5/17/2021 3:40 PM Carl Thompson wrote:
>
>
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CF
