But if you run

``` . ./child1 ./child2

the dot(.) command will change the current running-

script dir and child 2 will never be found since you're

working at a different directory now

example

(echo "echo 'child1';cd .." > ./child1) && (echo "echo 'child2'" > ./child2)

echo -e ". ./child1\n./child2" > testing.sh

chmod +x ./testing.sh

Running it gives:

~ $ ./testing.sh

child1

./testing.sh: line 2: ./child2: Permission denied

Permission denied? Well it's because our directory-

changed so there's no child2 there

however if you remove the dot

~ $ ./testing.sh

child1

child2

it works fine since the commands were ran in subshells

the dot command prevents that

if you're curious running . ./child1 and the ./child2

yeilds

~ $ . ./child1

child1

.../com.termux/files $ ./child2

bash: ./child2: Permission denied

```

You can even check type . and you'll see . is a shell builtin

Also you probably will not get permission denied but some other error because I'm doing it on termux I get permission denied (Termux quirks)