Differences between revisions 15 and 25 (spanning 10 versions)
Revision 15 as of 2013-12-21 22:32:02
Size: 1935
Editor: geirha
Comment: spam
Revision 25 as of 2014-04-24 10:02:07
Size: 2092
Editor: pgas
Comment: blank line breaking toc
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
Line 32: Line 31:
Line 39: Line 37:
and can be put into a helpful function:
Line 40: Line 39:
    # Bourne
    getarg() { # $1 is argno
        shift $1 && echo "$1"
    arg12="`getarg 12 "$@"`"
Line 48: Line 54:

How can I access positional parameters after $9?

Use ${10} instead of $10. This works for BASH and KornShell, but not for older BourneShell implementations. Another way to access arbitrary positional parameters after $9 is to use for, e.g. to get the last parameter:

    # Bourne
    for last
        : # nothing

    echo "last argument is: $last"

To get an argument by number, we can use a counter:

    # Bourne
    n=12        # This is the number of the argument we are interested in
    for arg
        if test $i -eq $n
        i=`expr $i + 1`
    echo "argument number $n is: $argn"

This has the advantage of not "consuming" the arguments. If this is no problem, the shift command discards the first positional arguments:

    shift 11
    echo "the 12th argument is: $1"

and can be put into a helpful function:

    # Bourne
    getarg() { # $1 is argno
        shift $1 && echo "$1"
    arg12="`getarg 12 "$@"`"

In addition, bash and ksh93 treat the set of positional parameters as an array, and you may use parameter expansion syntax to address those elements in a variety of ways:

    # Bash, ksh93
    for x in "${@:(-2)}"    # iterate over the last 2 parameters
    for y in "${@:2}"       # iterate over all parameters starting at $2
                            # which may be useful if we don't want to shift

Although direct access to any positional argument is possible this way, it's seldom needed. The common alternative is to use getopts to process options (e.g. "-l", or "-o filename"), and then use either for or while to process all the remaining arguments in turn. An explanation of how to process command line arguments is available in FAQ #35, and another is found at http://www.shelldorado.com/goodcoding/cmdargs.html


BashFAQ/025 (last edited 2014-04-24 10:02:07 by pgas)