On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote:
> looks like bash-4.0 has broken semicolon escaping in subshells. this comes
> up when using find's -exec like we do in a few places in eclasses:
> ls=$(find "$1" -name '*.po' -exec basename {} .po \;);
> shift you can work around the issue in a couple of ways:
> - quote the semicolon:
> .... ';')
> - use backticks
> `find .... \;`
>
> i'll tweak the eclasses to use quoting for now
> -mike
FYI. Not only find's semicolons are affected. It also happens in case ;;
construction.
--
Cheers,
Dawid Węgliński
