Re: Bash 4.3 handles array variables in sourced scripts differently than 4.2

On 3/10/14, 6:50 AM, "Chet Ramey" wrote: >On 3/9/14 8:45 PM, Ewan Mellor wrote: >> Hi, >> >> Please cc me ‹ I¹m not subscribed to this list. >> >> I have a script that works correctly in Bash 4.2.25(1)-release from >>Ubuntu >> 12.0

Bash 4.3 handles array variables in sourced scripts differently than 4.2

Hi, Please cc me ‹ I¹m not subscribed to this list. I have a script that works correctly in Bash 4.2.25(1)-release from Ubuntu 12.04 (package version 4.2-2ubuntu2) but that fails in Bash 4.3.0(1)-release from Ubuntu 14.04 prerelease (package version 4.3-2ubuntu1). The root of the problem is that

RE: set -e, bad substitutions, and trap EXIT

> -Original Message- > From: Chet Ramey [mailto:chet.ra...@case.edu] > Sent: Monday, February 13, 2012 5:05 AM > To: Ewan Mellor > Cc: Renuka Apte; bug-bash@gnu.org; chet.ra...@case.edu > Subject: Re: set -e, bad substitutions, and trap EXIT > > On 2/13/12 4:

RE: set -e, bad substitutions, and trap EXIT

> -Original Message- > From: Chet Ramey [mailto:chet.ra...@case.edu] > Sent: 08 February 2012 10:45 > To: Ewan Mellor > Cc: bug-bash@gnu.org; Renuka Apte; chet.ra...@case.edu > Subject: Re: set -e, bad substitutions, and trap EXIT > > On 2/6/12 8:18 PM, E

set -e, bad substitutions, and trap EXIT

Hi, Is this a bug? In the script below, I'm using a variable to control whether the script uses set -e or not, because the behavior is dependent on whether set -e is set. When the script hits the bad substitution, it runs the exit handler and then exits as expected. However, with set -e, the