ase the above: I don't think that you can mess up
these assignments or references with a file like "a0"; but you can do so
for `unset`.
--
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
hat
many people are unaware of.
(And in case it wasn't clear: I said that unset is different in the
expectations that people have with it, not in how it expands.)
--
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
On Thu, Oct 26, 2017 at 10:50 PM, Clark Wang wrote:
> On Fri, Oct 27, 2017 at 3:00 AM, Eli Barzilay wrote:
>>
>> 1. Drop the current "Care must be taken ... the entire array." two
>>sentences and replace them with some "See the unset builtin
>>d
t people don't miss it from
either place).
2. The parenthetical comment.
--
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
n Thu, Oct 26, 2017 at 8:56 AM, Chet Ramey wrote:
> On 10/26/17 1:18 AM, Eli Barzilay wrote:
>> Bash surprised me with the behavior mentioned here:
>>
>> https://stackoverflow.com/questions/15897473
>>
>> This can be pretty bad in that it's very unexpec
h the bash sources, and even there I found a few unsafe
uses:
grep -r 'unset[^a-z"'\'']*\[' examples tests
so this is clearly something that is not well-known enough.
--
((x=>x(x))(x=>x(x))) Eli Barzila
