1 |
On Sat, 2009-02-21 at 19:29 -0500, Mike Frysinger wrote: |
2 |
> On Saturday 21 February 2009 19:00:19 Mart Raudsepp wrote: |
3 |
> > On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote: |
4 |
> > > On Saturday 21 February 2009 18:38:55 Ryan Hill wrote: |
5 |
> > > > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote: |
6 |
> > > > > looks like bash-4.0 has broken semicolon escaping in subshells. this |
7 |
> > > > > comes up when using find's -exec like we do in a few places in |
8 |
> > > > > eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); |
9 |
> > > > > shift you can work around the issue in a couple of ways: |
10 |
> > > > > - quote the semicolon: |
11 |
> > > > > .... ';') |
12 |
> > > > > - use backticks |
13 |
> > > > > `find .... \;` |
14 |
> > > > > |
15 |
> > > > > i'll tweak the eclasses to use quoting for now |
16 |
> > > > |
17 |
> > > > is this a bug or broken on purpose? |
18 |
> > > |
19 |
> > > i say it's a bug, but i'm not the bash maintainer |
20 |
> > > |
21 |
> > > i imagine it's fall out from attempts to fix support for case statements |
22 |
> > > in subshells |
23 |
> > |
24 |
> > Then the bug should be fixed, instead of changing usage to something |
25 |
> > apparently less common, as the conversion could miss some. And more |
26 |
> > importantly users still want to use \; for find -exec ending on their |
27 |
> > command line and their very own scripts. |
28 |
> > And who knows how many shell scripts shipped by packages use the |
29 |
> > escaping method. |
30 |
> |
31 |
> i think you missed the entire point of this thread: there's a bug in bash-4.0 |
32 |
> that code is likely to hit. |
33 |
|
34 |
I think you missed the entire point of my reply. |
35 |
That bug should be fixed, not workarounds applied all over the tree, as |
36 |
users still want to be able to escape semi-colons. |
37 |
|
38 |
|
39 |
-- |
40 |
Mart Raudsepp |
41 |
Gentoo Developer |
42 |
Mail: leio@g.o |
43 |
Weblog: http://planet.gentoo.org/developers/leio |