| 1 |
On Saturday 21 February 2009 18:38:55 Ryan Hill wrote: |
| 2 |
> On Sat, 21 Feb 2009 18:27:10 -0500 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 |
| 5 |
> > eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift |
| 6 |
> > you can work 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 |
> is this a bug or broken on purpose? |
| 15 |
|
| 16 |
i say it's a bug, but i'm not the bash maintainer |
| 17 |
|
| 18 |
i imagine it's fall out from attempts to fix support for case statements in |
| 19 |
subshells |
| 20 |
-mike |
Archives