This post on bash scripts will quickly cover the topic of positional parameters. When it comes to bash scripts there are actually several sets of parameters to be aware of. There is the set of parameters that have to do with the bash command itself, there are a number of special parameters to work with, and then there is the set of parameters for the script that is called with bash. I have wrote a post on bash parameters in general, however in this post the focus will be just on positionals alone.
So In this post I will be going over a few quick examples of Linux bash scripts that make use of one or more arguments in the form of positional parameters that are given at the command line, or wherever the script is called.
So you want to learn what the deal is with parameters when writing a bash script. Well you have to start somewhere and maybe a good starting point is to lean how to access and make use of positional arguments. In this section I will be going over just a few quick examples of positionals.
When a bash script is called there might be one or more positional arguments that where passed when it was called. In fact even if no additional positionals where given when the script was called there is always at least one that is the file name of the script, or the name of the command that was called. Positionals start with the \$0 variable that will be the name of the command or script to begin with, followed by \$1 that will be the first argument, followed by \$2 that will be the second, and so on. These kinds of variables hold the state of the arguments that where given in order of there position from left to right starting with the command name, as such they are often called positional parameters.
So a Basic positional argument example bash script might look something like this:
I can then save this as something like basic.sh, and then call it in the command line. When doing so I can pass arguments to the script.
Although this is a post just on positional arguments alone I should take a moment to at least cover a few basic examples on special arguments in bash. There are a few special parameters in bash that can be used to get things like the name of the current script that is being called, and so forth. However when it comes to positional parameters there are two special parameters that comes to mind that might be the most important. One of which helps with getting a count of how many arguments where passed when the script is called, and the other is how to get a collection of all the arguments that where given.
So in this section I will be going over a few quick examples of special parameters in bash.
In this example I will be going over two special arguments that are the first two that I think are the most important when first starting out with writing basic bash scripts. One is the \$# special parameter that will give me the total count of positionals that where passed and the other is the \$\@ special parameter that will give me the full collection of positionals.
So if I have a basic bash script like this:
it will given me a count of arguments, and all the arguments
So then these two values can be used to create basic loops that will loop over all of the positionals and do something for each.
Now that I have covered not just the basics of positional parameters and a few basic special parameters I should also take a moment to write about the bash command itself. That command too can be passed a few arguments also that have to do with its own set of parameters. many of my bash scripts examples thus far involve making a bash script executable, to which it can then be called directly. However another options world be to call bash, then pass the script, and then pass some positionals for the script.
In other words something like this:
Here I am calling the bash command first and then using the c option that will make bash run the following string as a command. This then means that when a bash script is called there is yet another set of parameters to be aware of. There are the positionals, then the special parameters, and then there are the parameters of the bash command itself. This is why it is important to refer to positionals as such, to help elemnate confusion with all these other sets of parameters that are at play.
So then lets look at a few more examples of bash script parameters in general now.
Here I have a shell script that will just log out the current state of bash parameters, as well as positional parameters, by making use of two special parameters. So then this script can be though of as a basic script that makes use of the three different types of parameters in bash.
Now that I have this basic script worked out the state of what is logged out will depend on how it is called. So with that said lets now look at another script that will call this script in different ways. So lets save this above script as something like all.sh, and moive on to the next example.
There is calling a script directly if it has been set as executable with chmod, and then there is calling bash first and passing the script as an argument for the bash command. When calling bash a number of arguments can be given to the bash command, and the all.sh script that I just covered will log out the state of these options.
The positional parameters of a script are the first set of parameters that I have become aware of while learning bash. However there are of course a number of other sets of parameters that I should be aware of when writing bash scripts also. In addition there are other topics to write about when it comes to parameters in bash scripts. When it comes to basic scripts just working with positionals alone is okay, however what if I do make a bash script that can take up to say 10 arguments? With that said there should be a way to parse positional arguments into named arguments.
So one next step from here that might come to mind is to read my post on parsing positional arguments into named options by way of option parsing with the getopts bash built in command. There is also my main post on bash parameters in general also.