See:
$ echo $BASH_VERSION
5.1.0(1)-release
$
$ jobs
$ wait -n -p var
$ echo $var $?
66390280 127
If it left `var' unset that would be way more helpful to determine whether
one of the jobs exited with 127 or all the jobs were waited for and none
left.
Oğuz
Seems to be a minor mistake, even I could manage to fix it :D
diff --git a/builtins/wait.def b/builtins/wait.def
index 12260737..e25f7b5b 100644
--- a/builtins/wait.def
+++ b/builtins/wait.def
@@ -213,11 +213,11 @@ wait_builtin (list)
}
status = wait_for_any_job (wflags, &pstat);
+
I was trying the new features of bash 5.1 and came across this inconsistent
behavior:
$ foo='1 2'
$ declare -A bar=($foo 3)
$ declare -p bar
declare -A bar=(["\$foo"]="3" )
$
$ bar+=($foo 3)
$ declare -p bar
declare -A bar=(["\$foo"]="3" ["1 2"]="3" )
Is there a pa
Le 11/12/2020 à 13:08, Oğuz écrivait :
I was trying the new features of bash 5.1 and came across this inconsistent
behavior:
$ foo='1 2'
$ declare -A bar=($foo 3)
$ declare -p bar
declare -A bar=(["\$foo"]="3" )
$
$ bar+=($foo 3)
$ declare -p bar
declare -
On Fri, Dec 11, 2020 at 4:15 PM Léa Gris wrote:
> Le 11/12/2020 à 13:08, Oğuz écrivait :
> > I was trying the new features of bash 5.1 and came across this
> inconsistent
> > behavior:
> >
> > $ foo='1 2'
> > $ declare -A bar=($foo 3)
> > $ declare -p bar
> > declare -A bar=([
Date:Fri, 11 Dec 2020 13:25:01 +0300
From:=?UTF-8?B?T8SfdXo=?=
Message-ID:
| $ wait -n -p var
| $ echo $var $?
| 66390280 127
|
| If it left `var' unset
That's what the NetBSD sh does with this, it always explicitly unsets
the var given initially, and the
Le 11/12/2020 à 14:28, Oğuz écrivait :
Nah, this doesn't work either. Would be really useful if it did though.
$ declare -a foo=(1 2 )
$ declare -A assoc=("${foo[@]}" 3)
$ declare -p assoc
declare -A assoc=(["\"\${foo[@]}\""]="3" )
What would have been so useful is expandin
On 12/11/20 5:25 AM, Oğuz wrote:
See:
$ echo $BASH_VERSION
5.1.0(1)-release
$
$ jobs
$ wait -n -p var
$ echo $var $?
66390280 127
If it left `var' unset that would be way more helpful to determine whether
one of the jobs exited with 127 or all the jobs were waited for and none
left.
Thanks fo
On 12/11/20 7:08 AM, Oğuz wrote:
I was trying the new features of bash 5.1 and came across this inconsistent
behavior:
$ foo='1 2'
$ declare -A bar=($foo 3)
$ declare -p bar
declare -A bar=(["\$foo"]="3" )
$
$ bar+=($foo 3)
$ declare -p bar
declare -A bar=
On 12/11/20 9:45 AM, Léa Gris wrote:
Le 11/12/2020 à 14:28, Oğuz écrivait :
Nah, this doesn't work either. Would be really useful if it did though.
$ declare -a foo=(1 2 )
$ declare -A assoc=("${foo[@]}" 3)
$ declare -p assoc
declare -A assoc=(["\"\${foo[@]}\""]="3" )
What
This morning I downloaded bash-5.1-rc2. After I built it I ran 'make
check,. That produced (n
< fr_FR.ISO8859-1: Error Encoding U+0080 to [ "$'\200'" !=
"$'\302\200'" ]
... (124 similar errors)
< fr_FR.ISO8859-1: Error Encoding U+00FD to [ "$'\375'" != "ý" ]
< Failed 126 of 1378 Unic
On 12/11/20 2:02 PM, Douglas Lewan wrote:
This morning I downloaded bash-5.1-rc2. After I built it I ran 'make
check,. That produced (n
This is a longstanding problem with Debian. I've never been inclined to
look into it further. There is some issue with the French ISO8859-1
locale files that d
On 12/11/20 3:42 PM, Chet Ramey wrote:
On 12/11/20 2:02 PM, Douglas Lewan wrote:
This morning I downloaded bash-5.1-rc2. After I built it I ran 'make
check,. That produced
This is a longstanding problem with Debian. I've never been inclined to
look into it further. There is some issue with the
13 matches
Mail list logo
