On Sunday 22 February 2009 18:03:23 Dawid Węgliński wrote:
On Sunday 22 of February 2009 23:39:11 Mike Frysinger wrote:
On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote:
On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote:
looks like bash-4.0 has broken semicolon
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
On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote:
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'
On Sunday 22 of February 2009 23:39:11 Mike Frysinger wrote:
On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote:
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
On Sunday 22 February 2009 18:03:23 Dawid Węgliński wrote:
On Sunday 22 of February 2009 23:39:11 Mike Frysinger wrote:
On Sunday 22 February 2009 17:30:09 Dawid Węgliński wrote:
On Sunday 22 of February 2009 00:27:10 Mike Frysinger wrote:
looks like bash-4.0 has broken semicolon
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:
