1 |
On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote: |
2 |
> On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote: |
3 |
> > looks like bash-4.0 has broken semicolon escaping in subshells. this |
4 |
> > comes up when using find's -exec like we do in a few places in eclasses: |
5 |
> > ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift you can work |
6 |
> > around the issue in a couple of ways: |
7 |
> > - quote the semicolon: |
8 |
> > .... ';') |
9 |
> > - use backticks |
10 |
> > `find .... \;` |
11 |
> > |
12 |
> > i'll tweak the eclasses to use quoting for now |
13 |
> |
14 |
> FYI. Not only find's semicolons are affected. It also happens in case ;; |
15 |
> construction. |
16 |
|
17 |
embedded case statements in $(...) subshells have always been broken. |
18 |
bash-4.0 is supposed to fix that. if you have some code that is broken, |
19 |
please post it so i can push it upstream. |
20 |
-mike |