#!/bin/bashД®cho -e ' ^^^ Above file/dir exist! ^^^'ДЇollowing is the partial output to explain the situation.

However, due to exclude containing entries both with and without wildcard(*), and also they may not exist in all, extra checking is needed after the globbing of $i/$j. (I think you could play with -maxdepth on GNU find to limit how deep the search goes, if you care, but that's a bit of a different answer solved the main globbing issue. We have to use $HOME instead of ~ for the same reason as before, and $dirs needs to be unquoted on the find command line so it gets split, but $pattern should be quoted so it isn't accidentally expanded by the shell. home/foo/public/one/two/three/e2e/asdf.js to find any path ending in /e2e/*.js: $ dirs='$HOME/public $HOME/private' Something similar could be done with find -path, if you don't mind what directory level the targeted files should be. Though note that if the patterns don't match anything, they'll by default be left as-is. To work around this, use an array variable instead of a split string: $ IFS= home/foo/public/foo/hello.launch # not the expected result $ for j in $exclude do # glob, matches in current dir! So if the current directory contains something matching the pattern, it's expanded to that: $В IFS= Note that as $exclude is unquoted, it's both split, and also globbed at this point. When you loop over the patterns, as here: exclude='foo *bar' (* expanding globs from variables is usually not what you want) Tilde expansion happens before variable expansion so tildes inside variables are not expanded. The order of expansions is: brace expansion tilde expansion, parameter and variable expansion. $ mkdir -p ~/public/foo/ touch ~/public/foo/x.launch So, in the same vein, this is similar to what you did, and works: $ IFS= To prevent this issue, word splitting needs to be disabled by setting IFS to the empty string. Globbing happens after variable expansion, if the variable is unquoted, as here (*): $ x='/tm*' echo $xДЄnother thing that happens for unquoted expansions is word splitting, which will be an issue if the patterns in question contain characters in IFS, usually whitespace. (And eval starts having serious problems the moment your file names contain special characters like $.) The problem isn't with globbing, but with the tilde expansion. You can force another round of evaluation with eval, but that's not actually necessary. So I cannot hardcode the string in the for loop. In the long version below, you will see k=$i/$j. If I have a calculated string variable k, how do I make it glob in or right before a for-loop: i='~/code/public/*' My project directories are in ~/code/private/ and ~/code/public/ so I'm trying to use bash looping to do the tmutil. I want time machine to exclude a set of directories and files from all my git/nodejs project. Bash: GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16) Background

Os x shell script in global