Here's a small bash snippet #!/bin/bash x=(one two) echo ${x[@]:1} # prints nothing in bash3 # prints two as expected in bash2 x=(one two three) echo ${x[@]:1} #prints two three as expected in bash2 and bash3
UberLord, please file this to the bash maintainers using bashbug. (But thanks for filing it here first, that is the right thing to do.)
Done.
I've never been sure of the meaning of Resolved UPSTREAM, but it seems to make sense here.
Created attachment 37579 [details, diff] Fixes the problem described Chet Ramey forwarded me this patch with i included as the first patch in the current ebuild which fixes the problem above :)
ok, I added this to bash-3.0-r5
