Re: Cannot clone from anonymous git

2016-05-14 Thread Piotr Grzybowski
yeah, started yesterday, seems like a reaource allocation problem, I would avoid clones, if possible, and fetch only certain branches. if you already have a piece of repo that is. usually pulls work after a couple of tries. pg El 13/05/2016 23:41, "Mike Frysinger" escribió: > On 13 May 2016 15:4

Re: param expansion with single-character special vars in the environment

2016-05-14 Thread Grisha Levit
One more case, which currently segfaults: declare -n REPLY; read <<< / easy fix: diff --git a/builtins/read.def b/builtins/read.def index 5e2348c..8f6bd2b 100644--- a/builtins/read.def+++ b/builtins/read.def @@ -797,9 +797,11 @@ assign_vars: } else var = bind_variable ("RE

Re: param expansion with single-character special vars in the environment

2016-05-14 Thread Grisha Levit
On Mon, May 2, 2016 at 2:30 PM, Chet Ramey wrote: I ended up writing a new function: valid_nameref_value(name, flags) which > I can customize to serve this purpose. > Looks like this ends up getting bypassed in some cases when the value is an empty string: declare -n r; : ${r=}declare -n r; r=""

Re: declare [-+]n behavior on existing (chained) namerefs

2016-05-14 Thread Piotr Grzybowski
On 13 May 2016, at 23:31, Grisha Levit wrote: > All the behavior inside functions now seems consistent with what is in the > docs. But the behavior at global scope still seems strange (sorry if this is > still a WIP): > Each of the following produces different results in global scope and inside

Re: param expansion with single-character special vars in the environment

2016-05-14 Thread Piotr Grzybowski
hi, there are two problems: not checking NULL returned by bind_variable, and not allowing to enter valid_nameref_value. Since bind_variable can return NULL, that should be checked everywhere. Also NULL and empty strings are not valid nameref values, so the check should be added in valid_namer