Question

When the following two lines of code are executed in a bash script, ‘ls’ complains that the files don’t exist:

dirs=/content/{dev01,dev02} ls -l $dirs 

When I run the script with the -x option, it appears to be passing the variable within single quotes (which would prevent globbing):

+ dirs=/content/{dev01,dev01} + ls -l '/content/{dev01,dev01}' ls: /content/{dev01,dev01}: No such file or directory 

If I execute the ‘ls’ command from my interactive shell (sans quotes), it returns the two directories.

I’ve been reading through the Bash Reference Manual (v 3.2) and can’t see any reason for filename globbing to not take place (I’m not passing -f to the shell), or anything that I can set to ensure that globbing happens.

Answer 1

I think it is the order of expansions:

The order of expansions is: brace expansion, tilde expansion, parameter, variable and arithmetic expansion and command substitution (done in a left-to-right fashion), word splitting, and pathname expansion.

So if your variable is substituted, brace expansion doesn’t take place anymore. This works for me:

eval ls $dirs 

Be very careful with eval. It will execute the stuff verbatimly. So if dirs contains f{m,k}t*; some_command, some_command will be executed after the ls finished. It will execute the string you give to eval in the current shell. It will pass /content/dev01 /content/dev02 to ls, whether they exist or not. Putting * after the stuff makes it a pathname-expansion, and it will omit non-existing paths:

dirs=/content/{dev01,dev02}* 

I’m not 100% sure about this, but it makes sense to me.