There are so many different ways to create bash loops. Let's just look at a few. After the first, I'll only list the initial line:
for i in 1 2 3 4 cow do echo $i done # alternate: for i in 1 2 3 4 cow; do echo $i;done for i in `seq 1 10` for ((j=1; j <= 10; j+=2)) while ((x++ < 10)) until ((x-- < -10)) for i in $(ls) for in in `cat /tmp/somefile`
Two other commands are useful within loops: "break" exits a loop, and "continue" goes to the next iteration:
for i in 1 2 3 4 cow 6 7 8 do # skips "cow" ((i * 1 == 0)) && continue echo $i done for i in 1 2 3 4 cow 6 7 8 do # stops after "4" ((i * 1 == 0)) && break echo $i done
Arrays can be looped:
array=(one two three)
for x in ${array[@]}
do
echo $x
done
array=(one two three)
for ((x=0; x < ${#array[@]} ; x++))
do
echo ${array[$x]}
done
A problem that often comes up for new users is looping over certain files. For example, you might want to do something to every .txt file:
for i in *.txt do something $i done
That works, but if there are no ".txt" files, "something" gets passed "*.txt" just the same. If that's not a good thing, you need to do more:
if `ls *.txt > /dev/null 2>&1` then for i in *.txt do something $i done fi
Or you might do something like this:
count=`ls *.txt 2>/dev/null | wc -l` if [ "$count" -gt 0 ] then echo "$count files to back up" for i in *.txt do something $i done fi
Yet another way to do something like that is:
set -- *.txt [ -f "$1" ] && dosomething *.txt
If the set gets nothing, $1 will be empty. Another advantage is that you don't loop over each file if you don't need to.
As you've seen, there are a lot of different ways to do bash looping. Which you use depends mostly on on what you are trying to accomplish, and to a lesser extent on your own style and preferences.
More Articles by Tony Lawrence - Find me on Google+
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Mon Aug 8 14:46:51 2011: TonyLawrence
Now that Bash 3 is becoming more common (with Bash 4 lagging behind), you should also see Bash 3 brace expansion http://aplawrence.com/Linux/brace-expansion.html
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar