Here was an interesting bug which was some what unexpected.
cat <(find ./ -iname t{1,2,3})
this is a valid command according to bash due to a bugged expansion of
{1,2,3} and the process expansion. It becomes three commands:
find ./ -iname t1
find ./ -iname t2
find ./ -iname t3
but as we know
find ./ -iname t{1,2,3}
is not a valid command, and the expansion behaviour is drasticly changed
while in the <(...)
although this
behaviour can be avoided by wrapping it up in things like "..." or $(...)
cat <(eval "find ./ -iname t{1,2,3}")
errors as expected and does not launch the three processes.
I feel that the expansion should be protected wheither wrapped or not to
preserve the expected results.
Please keep me posted on this bug.
Michael
_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
