I am learning unix shell scripting. I want to create a utiltiy. I will explain about that. When I run my utility, it will display only the directories of a particular directory like the below output. For example
My current directory is /home/balamv and it has 3 directories called Andrew, Jason, Malar. Hence the output is
Andrew
Jason
Malar
Chose option : 2
Processing . . .
The main thing here is, this should be generic and if I run this from any directory and it should display all the directories present and also the number sequence. If 20 directories are there, then the options will come till 20.
Anyone could pls help me on this? Thanks in advance.
You can use arrays in either ksh or bash. I don't have ksh in front of me, so here's bash. Note that this assumes your directory names don't have spaces in them:
cd /path/to/your/dirs
dirs="not_using_0"
for entry in *; do
[ -d "$entry" ] && dirs="$dirs $entry"
done
dirarray=($dirs)
index=1
while [ -n "${dirarray[$index]}" ] ; then
echo "${index}: ${dirarray[$index]}"
index=`expr $index + 1`
done
while [ -z "$ans" ] ; do
echo -n "Choose one -> "
read ans
[ -z "${dirarray[$ans]}" ] && echo "Invalid response; try again."
done
echo "Result is ${dirarray[$ans]}"
mschwage, It works Great
But I can't unerstand why u gave the value of "not_using_0 to dirs, as balamv asked ??
balamv,about the for statement, it test all items in the current directory if it is a directory, add it's value to dirs, and so on.
Note: replace then with do @line 8 to work properly.
I got the answer of my and balamv question, "not_using_0" was assigned to dirs in the first position, and the index was began from the position 1, so it is no matter what is the first element, as we move directly to the second one.
For Example:
arrayname[value1 value2 value3]
to get the value1 echo ${arrayname[0]}
to get the value2 echo ${arrayname[1]}
and so on
I see you have some of your answers already, but just to make sure this is crystal clear:
First, I recommend programming in ksh. Bash is nice, but it may not be available on all architectures that you may work with. Ksh is more portable and has enough programming features to keep you happy for a while.
Next: Starting with "0" as the beginning element of a list or array is a programmer's thing. End users don't usually count starting with 0. So I make sure to fill the 0'th element of the array with something silly that will never be used.
Finally, this:
for entry in *; do
[ -d "$entry" ] && dirs="$dirs $entry"
done
...is kind of tricky for a new person. It was years before I learned it. Here's the explanation:
Let's say you do an "ls" in your home directory:
ls
And let's say you have 2 files and two subdirectories. So the results of ls may be:
dir1 dir2 file1 file2
Now- I'm going to get off track for a second- if you wanted to look for the string "mschwage" in all your files, you might do something like
grep mschwage f*
. What happens when you type that command to the shell? A number of things:
The shell analyzes your line, looking for metacharacters
It finds the asterisk, which is attached to the f
It looks at all the entries (files and directories) in your current directory, and does a pattern match. All files that begin with f followed by anything (or nothing at all) are matched.
The results of that pattern match become the arguments to "grep"
Notice: the shell hands the argument list to grep. Grep never sees an asterisk.. You need to be aware of how the shell processes command lines.
Now, back to the for loop: Here-
for entry in *
the asterisk matches everything in your current directory. In this example, it will match
dir1 dir2 file1 file2
Each one of those entries then, is assigned to the variable "entry", one by one, for each cycle through the loop. So after the shell expands the asterisk, the line looks like:
for entry in dir1 dir2 file1 file2; do
Next, I test each one of those entries and, if it IS a directory, append it to the "dirs" variable. So when all is said and done, dirs will look like:
not_using_0 dir1 dir2
...a list of 3 items, in this case. Every entry in dirs, starting with item 1 (not item 0), is a directory in the current directory.
No problem. Shell scripting is weird. I've been doing it since 1983 and it's still weird. Happy to help.
Perl is much better, but still weird.
I'm going to start learning Python. I think that will be a much better scripting language.
-mschwage
P.S. Definition of weird: Writing a 600 line shell script and forgetting to match the double-quotes in a string somewhere around line 200. Tracking down that error is part of the definition of 'pain'. Shell scripting is essential on UNIX, but oh boy...
