[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Variation" in Command Substitution Behaviour
From: |
Reuti |
Subject: |
Re: "Variation" in Command Substitution Behaviour |
Date: |
Wed, 1 Mar 2017 21:32:50 +0100 |
Am 01.03.2017 um 21:24 schrieb Grisha Levit:
> On Wed, Mar 1, 2017 at 3:08 PM, Reuti <reuti@staff.uni-marburg.de> wrote:
>> I would say not closed, as it's still happening in 4.4.12. And if it's
>> closed, it should be reopened.
>
> Are you using the same example? I can reproduce Geoff's original test
> case with 4.3 but not with 4.4..
Ok, I can't reproduce the issue he found - correct this is gone. But the
behavior I found:
bash-4.4$ reset_vars
bash-4.4$ assemble_fam2
bash-4.4$ assemble_fam1
bash-4.4$ say_families
Flintstones=wilma:bam-bam:fred
Rubbles=barney
is still there.
-- Reuti
- Re: "Variation" in Command Substitution Behaviour, Geoff Hull, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour, Reuti, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour, Grisha Levit, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour, Reuti, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour, Geoff Hull, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour, Reuti, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour, Grisha Levit, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour,
Reuti <=
- Re: "Variation" in Command Substitution Behaviour, Chet Ramey, 2017/03/01
- Re: "Variation" in Command Substitution Behaviour, Reuti, 2017/03/01