There are two different ways of parsing command line arguments while using
getopt(3). There is an utility called getopt (
man 1 getopt). This
utility is available in all shells. Then in bash, there is another built-in
tool for parsing arguments called getopts (it’s a built-in, so it
doesn’t have it’s own man-page – try
Here’s an example script that demonstrates the usage of getopt:
At first, the getopt utility is called with desired parameters (see man getopt for detailed description of all the options). If it returns anything else than 0, something was wrong and we’ll end the script. There is no error message necessary, because the getopt itself will inform user about what went wrong. After that, there’s a little magic line with eval and set. It’s there to preserve whitespaces inside options arguments. Detailed description of this technique is here. All options are evaluated and appropriate actions take place in the while loop at the end of the script.
Here’s an example script that demonstrates the usage of getopts:
As you can see, the bash built-in version is easier to use, but it can’t
handle long options like
Which one you should use? Well, it’s up to you, what you need. If you’re looking for compatibility of your script among more shells than just bash or want to have long options, you’ll need to use the getopt utility. If not, I’d go for the getopts built-in, which I personally consider more user-friendly.