Re: find: support all shell wildcards

[eavis]

[supporting {} wildcards with find -name]

>First, it bash extension, it is incompatible with traditional Bourne
>style shells.

But bash is the standard shell for GNU, so find ought to support the same 
wildcards.

>Another, more important argument is this: in bash, brace expansion
>presents a separate step, it's not part of pattern expansion.  That is
>why it works even if the files do not exist:
>                touch {a,b}

This is true but I don't see how this difference is relevant for find. 
Find's patterns are tested against filenames one at a time, at least 
conceptually.

>To conclude, I beleive it's not a bug but a request for enhancement.

In that case I would request that you consider this enhancement.

Personally, I feel that the advantage of having the same patterns 
supported by both find and the shell outweighs any philosophical concerns 
about {} being different to the other wildcards when it is used in bash. 
In any case, if find does not support {} wildcards then this should be 
explicitly mentioned in the documentation, since just saying 'shell 
wildcards' might lead many users to think they could use exactly the same 
patterns as in the shell.

-- 
Ed Avis <address@hidden>