On 4/2/11 3:59 PM, Michael Witten wrote:
> Thus, bash has a bug.
>
> My guess is the nature of the problem is that the combination
> of the outer-most quotes (which would render most characters
> as literal) and the command substitution (which in some sense
> is probably parsed in a `top-level' context) works to confuse
> the brace-expansion logic.
Pretty close. The brace expansion code doesn't really know very
much shell syntax. It does know about command and process substitution,
but only when unquoted. The fix for this is to handle command
substitution when processing a double-quoted string. That will be
in the next bash release, at least.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
