Signed-off-by: Ismael Luceno
---
lib/sh/strtoimax.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/lib/sh/strtoimax.c b/lib/sh/strtoimax.c
index 584fa0ba20f5..7deab27bd692 100644
--- a/lib/sh/strtoimax.c
+++ b/lib/sh/strtoimax.c
@@ -20,9 +20,9 @@
/* Written by Paul
On Tue, Jul 2, 2024 at 9:59 PM Zachary Santer wrote:
>
> I *am* seeing a difference between having lastpipe enabled (and job
> control off) or not when running your example in the interactive
> shell, though:
> SECONDS=0; echo $'foo\nbar' | tee >(echo first ; exit 1) >(wc ; sleep
> 10 ; echo wc) >
On Tue, Jul 2, 2024 at 4:56 PM Mark March wrote:
>
> lastpipe takes effect only if job control is off. From the man page:
>
> lastpipe
> If set, and job control is not active, the shell
>
> With laspipe on and job control off, 'wait' appears to wait for all process
lastpipe takes effect only if job control is off. From the man page:
lastpipe
If set, and job control is not active, the shell
With laspipe on and job control off, 'wait' appears to wait for all process
substitutions:
set +mshopt -s lastpipe
echo $'foo\nbar' | tee
On 7/2/24 3:04 PM, Emanuele Torre wrote:
From the bash man page:
compat43
• the shell does not print a warning message if an attempt
is made to use a quoted compound assignment as an argument
to declare (e.g., declare -a foo='(1 2)'). Later versio
>From the bash man page:
compat43
• the shell does not print a warning message if an attempt
is made to use a quoted compound assignment as an argument
to declare (e.g., declare -a foo='(1 2)'). Later versions
warn that this usage is depreca
