Re: . (source) builtin behavior changed when commands are in {} braces

2008-08-17 Thread Chet Ramey
Roman Rakus wrote: It's strange. Now I build bash with only official patches. Version 3.2.39. Hello isn't printed. If I don't use patch 20, then Hello is printed. I'm using this command: ./bash -c ". ~/tmp/bash/braces/test.sh" Did you use . builtin? I must not have, because when I use it n

Re: . (source) builtin behavior changed when commands are in {} braces

2008-08-17 Thread Roman Rakus
Chet Ramey wrote: Roman Rakus wrote: In previous version (3.0) bash continue after {} braces. For example: { readonly a a=10 } || : echo hello In bash 3.2 we've got error message about readonly variable, but "hello" is not printed. Is this right behavior or bug? I'm not sure what changes

Re: . (source) builtin behavior changed when commands are in {} braces

2008-08-15 Thread Chet Ramey
Roman Rakus wrote: In previous version (3.0) bash continue after {} braces. For example: { readonly a a=10 } || : echo hello In bash 3.2 we've got error message about readonly variable, but "hello" is not printed. Is this right behavior or bug? I'm not sure what changes you've made to the

. (source) builtin behavior changed when commands are in {} braces

2008-08-15 Thread Roman Rakus
In previous version (3.0) bash continue after {} braces. For example: { readonly a a=10 } || : echo hello In bash 3.2 we've got error message about readonly variable, but "hello" is not printed. Is this right behavior or bug? I investigate this problem and found, that there is added top_lev