如何在bash中使用getopts的示例


345

我想以myscript这种方式调用文件:

$ ./myscript -s 45 -p any_string

要么

$ ./myscript -h  #should display help
$ ./myscript     #should display help

我的要求是:

  • getopt 在这里获取输入参数
  • 检查是否-s存在,如果不返回错误
  • 检查后面的值-s是45还是90
  • 检查是否-p存在并且在输入字符串之后
  • 如果用户输入./myscript -h或仅./myscript显示帮助

到目前为止,我尝试了以下代码:

#!/bin/bash
while getopts "h:s:" arg; do
  case $arg in
    h)
      echo "usage" 
      ;;
    s)
      strength=$OPTARG
      echo $strength
      ;;
  esac
done

但是用该代码我得到了错误。如何使用Bash和getopt


2
选项应该是可选的。如果需要由指定的值-s,请将其设置为位置参数:./myscript 45 anystring
chepner 2013年

@chepner$./myscript -s 45 -p any_string
MOHAMED

如果-p实际上是一个选项,那就很好(也就是说,如果程序不存在,您的程序可以继续执行)。在这种情况下,./myscript 45 -p any_string。(我认为这getopt可以处理混合的选项和位置参数,而bash内置命令getopts要求将所有位置参数都放在选项之后。)
chepner 2013年

Answers:


513
#!/bin/bash

usage() { echo "Usage: $0 [-s <45|90>] [-p <string>]" 1>&2; exit 1; }

while getopts ":s:p:" o; do
    case "${o}" in
        s)
            s=${OPTARG}
            ((s == 45 || s == 90)) || usage
            ;;
        p)
            p=${OPTARG}
            ;;
        *)
            usage
            ;;
    esac
done
shift $((OPTIND-1))

if [ -z "${s}" ] || [ -z "${p}" ]; then
    usage
fi

echo "s = ${s}"
echo "p = ${p}"

示例运行:

$ ./myscript.sh
Usage: ./myscript.sh [-s <45|90>] [-p <string>]

$ ./myscript.sh -h
Usage: ./myscript.sh [-s <45|90>] [-p <string>]

$ ./myscript.sh -s "" -p ""
Usage: ./myscript.sh [-s <45|90>] [-p <string>]

$ ./myscript.sh -s 10 -p foo
Usage: ./myscript.sh [-s <45|90>] [-p <string>]

$ ./myscript.sh -s 45 -p foo
s = 45
p = foo

$ ./myscript.sh -s 90 -p bar
s = 90
p = bar

19
在getopts调用中,为什么会有前导冒号?什么时候“ h”在其后有一个冒号?
e40 2013年

6
应该usage()真的返回1吗?
Pithikos

6
@Pithikos好点。常识告诉我,通过-h它调用时应返回0,当击中不存在的标志时应返回>0(为简单起见,我没有区分这些情况,没有人强迫您在后一种情况下打印用法文本) 。我看过的程序!= 0即使在上也总是返回-h/--help。如果人们将其用作样板,也许我应该更新代码片段(我希望不是)?
AdrianFrühwirth2014年

1
@ A.Danischewski这是通过(getopts')设计的,没有类似“可选参数”的东西getopts。解析器根本无法知道下一个标记是当前选项的参数还是它本身的选项,因为它-p可能是预期值。如果您绝对知道一个选项参数看起来不能像另一个有效选项,那么您可以解决这个问题,是的,但是您可能会说,有一个原因导致未在POSIX中定义可选参数。
AdrianFrühwirth'15

4
@ user1011471你是对的!可以说,花括号可以帮助bash词法分析器识别变量。在许多情况下,它们是不需要的,而我始终使用它们的事实只是个人编码风格的问题。对我来说,仅使用它们而不是记住关于歧义的解析规则会更容易(更漂亮)。为什么要写if (foo) { bar; }而不是if (foo) bar;用C风格的语言(美学和/或避免愚蠢的错误)几乎相同。
AdrianFrühwirth15年

108

原始代码的问题是:

  • h:期望参数在不应该的位置,因此将其更改为正h(无冒号)
  • 期望-p any_string,您需要添加p:到参数列表

基本上:,选项表示需要参数。


的基本语法getopts是(请参阅:)man bash

getopts OPTSTRING VARNAME [ARGS...]

哪里:

  • OPTSTRING 是带有期望参数列表的字符串,

    • h-检查-h 没有参数的选项;在不支持的选项上给出错误;
    • h:-检查-h 带有参数的选项;在不支持的选项上给出错误;
    • abc-检查选项-a-b-c,在不支持的选项上给出错误;
    • :abc-检查选项-a-b-c使不支持的选项上的错误静音;

      注意:换句话说,选项前的冒号允许您处理代码中的错误。?如果选项不受支持,:则值将包含变量。

  • OPTARG -设置为当前参数值,

  • OPTERR -指示Bash是否应显示错误消息。

因此代码可以是:

#!/usr/bin/env bash
usage() { echo "$0 usage:" && grep " .)\ #" $0; exit 0; }
[ $# -eq 0 ] && usage
while getopts ":hs:p:" arg; do
  case $arg in
    p) # Specify p value.
      echo "p is ${OPTARG}"
      ;;
    s) # Specify strength, either 45 or 90.
      strength=${OPTARG}
      [ $strength -eq 45 -o $strength -eq 90 ] \
        && echo "Strength is $strength." \
        || echo "Strength needs to be either 45 or 90, $strength found instead."
      ;;
    h | *) # Display help.
      usage
      exit 0
      ;;
  esac
done

用法示例:

$ ./foo.sh 
./foo.sh usage:
    p) # Specify p value.
    s) # Specify strength, either 45 or 90.
    h | *) # Display help.
$ ./foo.sh -s 123 -p any_string
Strength needs to be either 45 or 90, 123 found instead.
p is any_string
$ ./foo.sh -s 90 -p any_string
Strength is 90.
p is any_string

请参阅:Bash Hackers Wiki上的Small getopts教程


2
将用法功能更改为此:usage() { echo "$0 usage:" && grep "[[:space:]].)\ #" $0 | sed 's/#//' | sed -r 's/([a-z])\)/-\1/'; exit 0; }。它仅在字母选项前占一个空格字符,从注释中删除#,并在字母选项前加上“-”,使命令更清晰。
poagester,

2
@kenorb:选项前面的冒号不会忽略不支持的选项,但是会消除bash中的错误并允许您在代码中进行处理。变量将包含“?” 如果选项不受支持,则值丢失时为“:”。
海尼克

1
感谢您提供详细的文档,:直到我看到这些说明后才能够正确使用。我们需要:在期望参数的选项中添加一个。
奥汉(Aukhan)

51

采用 getopt

为什么要选择?

要解析详细的命令行参数以避免混淆并阐明我们正在解析的选项,以便使命令的读者可以了解正在发生的事情。

什么是getopt?

getopt用于在命令行中分解(解析)选项,以方便shell过程进行解析,并检查合法选项。它使用GNU getopt(3)例程执行此操作。

getopt 可以具有以下类型的选项。

  1. 无价值选择
  2. 键值对选项

注意:在本文中,在解释语法期间:

  • []内的所有内容在语法/示例中均为可选参数。
  • 是一个占位符,表示应替换为实际值。

如何使用getopt

语法:第一种形式

getopt optstring parameters

例子:

# This is correct
getopt "hv:t::" "-v 123 -t123"  
getopt "hv:t::" "-v123 -t123"  # -v and 123 doesn't have whitespace

# -h takes no value.
getopt "hv:t::" "-h -v123"


# This is wrong. after -t can't have whitespace.
# Only optional params cannot have whitespace between key and value
getopt "hv:t::" "-v 123 -t 123"

# Multiple arguments that takes value.
getopt "h:v:t::g::" "-h abc -v 123 -t21"

# Multiple arguments without value
# All of these are correct
getopt "hvt" "-htv"
getopt "hvt" "-h -t -v"
getopt "hvt" "-tv -h"

这里的h,v,t是选项,-h -v -t是应该在命令行中给出选项的方式。

  1. “ h”是无值选项。
  2. 'v:'表示选项-v具有值,并且是强制性选项。“:”表示具有值。
  3. 't ::'表示选项-t具有值,但是可选的。'::'表示可选。

在可选参数中,值不能与选项分隔。因此,在“ -t123”示例中,-t是选项123的值。

语法:第二种形式

getopt [getopt_options] [--] [optstring] [parameters]

在将getopt分为五个部分之后

  • 命令本身即getopt
  • getopt_options,它描述了如何解析参数。单破折号长选项,双破折号选项。
  • -,将getopt_options与要解析的选项和允许的简短选项分开
  • 简短选项-找到后立即采取。就像Form first语法一样。
  • 参数,这些是您传递到程序中的选项。您要解析的选项并获取在其上设置的实际值。

例子

getopt -l "name:,version::,verbose" -- "n:v::V" "--name=Karthik -version=5.2 -verbose"

语法:第三形式

getopt [getopt_options] [-o options] [--] [optstring] [parameters]

在将getopt分为五个部分之后

  • 命令本身即getopt
  • getopt_options,它描述了如何解析参数。单破折号长选项,双破折号选项。
  • 简短选项,即-o或--options。就像Form first语法一样,但选项为“ -o”且在“-”之前(双破折号)。
  • -,将getopt_options与要解析的选项和允许的简短选项分开
  • 参数,这些是您传递到程序中的选项。您要解析的选项并获取在其上设置的实际值。

例子

getopt -l "name:,version::,verbose" -a -o "n:v::V" -- "-name=Karthik -version=5.2 -verbose"

GETOPT_OPTIONS

getopt_options更改了解析命令行参数的方式。

以下是一些getopt_options

选项:-l或--longoptions

意味着getopt命令应允许识别多字符选项。多个选项用逗号分隔。

例如,--name=Karthik是在命令行中发送的长选项。在getopt中,长选项的用法就像

getopt "name:,version" "--name=Karthik"

由于指定了name :,因此该选项应包含一个值

选项:-a或--alternative

意味着getopt命令应允许long选项使用单破折号'-'而不是双破折号'-'。

例如,--name=Karthik您可以只使用-name=Karthik

getopt "name:,version" "-name=Karthik"

带有代码的完整脚本示例:

#!/bin/bash

# filename: commandLine.sh
# author: @theBuzzyCoder

showHelp() {
# `cat << EOF` This means that cat should stop reading when EOF is detected
cat << EOF  
Usage: ./installer -v <espo-version> [-hrV]
Install Pre-requisites for EspoCRM with docker in Development mode

-h, -help,          --help                  Display help

-v, -espo-version,  --espo-version          Set and Download specific version of EspoCRM

-r, -rebuild,       --rebuild               Rebuild php vendor directory using composer and compiled css using grunt

-V, -verbose,       --verbose               Run script in verbose mode. Will print out each step of execution.

EOF
# EOF is found above and hence cat command stops reading. This is equivalent to echo but much neater when printing out.
}


export version=0
export verbose=0
export rebuilt=0

# $@ is all command line parameters passed to the script.
# -o is for short options like -v
# -l is for long options with double dash like --version
# the comma separates different long options
# -a is for long options with single dash like -version
options=$(getopt -l "help,version:,verbose,rebuild,dryrun" -o "hv:Vrd" -a -- "$@")

# set --:
# If no arguments follow this option, then the positional parameters are unset. Otherwise, the positional parameters 
# are set to the arguments, even if some of them begin with a ‘-’.
eval set -- "$options"

while true
do
case $1 in
-h|--help) 
    showHelp
    exit 0
    ;;
-v|--version) 
    shift
    export version=$1
    ;;
-V|--verbose)
    export verbose=1
    set -xv  # Set xtrace and verbose mode.
    ;;
-r|--rebuild)
    export rebuild=1
    ;;
--)
    shift
    break;;
esac
shift
done

运行此脚本文件:

# With short options grouped together and long option
# With double dash '--version'

bash commandLine.sh --version=1.0 -rV
# With short options grouped together and long option
# With single dash '-version'

bash commandLine.sh -version=1.0 -rV

# OR with short option that takes value, value separated by whitespace
# by key

bash commandLine.sh -v 1.0 -rV

# OR with short option that takes value, value without whitespace
# separation from key.

bash commandLine.sh -v1.0 -rV

# OR Separating individual short options

bash commandLine.sh -v1.0 -r -V


getopt vs getopts ..跨平台合规性非常不同
shadowbq

35

getopt(我的发行版放入/usr/share/getopt/getopt-parse.bash)一起打包的示例似乎涵盖了您的所有情况:

#!/bin/bash

# A small example program for using the new getopt(1) program.
# This program will only work with bash(1)
# An similar program using the tcsh(1) script language can be found
# as parse.tcsh

# Example input and output (from the bash prompt):
# ./parse.bash -a par1 'another arg' --c-long 'wow!*\?' -cmore -b " very long "
# Option a
# Option c, no argument
# Option c, argument `more'
# Option b, argument ` very long '
# Remaining arguments:
# --> `par1'
# --> `another arg'
# --> `wow!*\?'

# Note that we use `"$@"' to let each command-line parameter expand to a 
# separate word. The quotes around `$@' are essential!
# We need TEMP as the `eval set --' would nuke the return value of getopt.
TEMP=`getopt -o ab:c:: --long a-long,b-long:,c-long:: \
     -n 'example.bash' -- "$@"`

if [ $? != 0 ] ; then echo "Terminating..." >&2 ; exit 1 ; fi

# Note the quotes around `$TEMP': they are essential!
eval set -- "$TEMP"

while true ; do
    case "$1" in
        -a|--a-long) echo "Option a" ; shift ;;
        -b|--b-long) echo "Option b, argument \`$2'" ; shift 2 ;;
        -c|--c-long) 
            # c has an optional argument. As we are in quoted mode,
            # an empty parameter will be generated if its optional
            # argument is not found.
            case "$2" in
                "") echo "Option c, no argument"; shift 2 ;;
                *)  echo "Option c, argument \`$2'" ; shift 2 ;;
            esac ;;
        --) shift ; break ;;
        *) echo "Internal error!" ; exit 1 ;;
    esac
done
echo "Remaining arguments:"
for arg do echo '--> '"\`$arg'" ; done

11
外部命令getopt(1)永远不会安全使用,除非您知道它是GNU getopt,并以GNU特定的方式调用它,确保GETOPT_COMPATIBLE不在环境中。请改用getopts(内置的shell),或简单地在位置参数上循环。
吉尔·奎诺

@ sputnick,tyvm,不知道这一点。
Brian Cain

14
h,按照该标准,没有安全的外部命令可以使用。内置的getopts缺少关键功能,如果要检查GETOPT_COMPATIBLE,则比移植getopt的功能容易。
迈克尔·特里

12

我知道已经回答了这个问题,但是为了记录以及与我有同样要求的任何人,我决定发布此相关答案。该代码充满注释以解释该代码。

更新的答案:

将文件另存为getopt.sh

#!/bin/bash

function get_variable_name_for_option {
    local OPT_DESC=${1}
    local OPTION=${2}
    local VAR=$(echo ${OPT_DESC} | sed -e "s/.*\[\?-${OPTION} \([A-Z_]\+\).*/\1/g" -e "s/.*\[\?-\(${OPTION}\).*/\1FLAG/g")

    if [[ "${VAR}" == "${1}" ]]; then
        echo ""
    else
        echo ${VAR}
    fi
}

function parse_options {
    local OPT_DESC=${1}
    local INPUT=$(get_input_for_getopts "${OPT_DESC}")

    shift
    while getopts ${INPUT} OPTION ${@};
    do
        [ ${OPTION} == "?" ] && usage
        VARNAME=$(get_variable_name_for_option "${OPT_DESC}" "${OPTION}")
            [ "${VARNAME}" != "" ] && eval "${VARNAME}=${OPTARG:-true}" # && printf "\t%s\n" "* Declaring ${VARNAME}=${!VARNAME} -- OPTIONS='$OPTION'"
    done

    check_for_required "${OPT_DESC}"

}

function check_for_required {
    local OPT_DESC=${1}
    local REQUIRED=$(get_required "${OPT_DESC}" | sed -e "s/\://g")
    while test -n "${REQUIRED}"; do
        OPTION=${REQUIRED:0:1}
        VARNAME=$(get_variable_name_for_option "${OPT_DESC}" "${OPTION}")
                [ -z "${!VARNAME}" ] && printf "ERROR: %s\n" "Option -${OPTION} must been set." && usage
        REQUIRED=${REQUIRED:1}
    done
}

function get_input_for_getopts {
    local OPT_DESC=${1}
    echo ${OPT_DESC} | sed -e "s/\([a-zA-Z]\) [A-Z_]\+/\1:/g" -e "s/[][ -]//g"
}

function get_optional {
    local OPT_DESC=${1}
    echo ${OPT_DESC} | sed -e "s/[^[]*\(\[[^]]*\]\)[^[]*/\1/g" -e "s/\([a-zA-Z]\) [A-Z_]\+/\1:/g" -e "s/[][ -]//g"
}

function get_required {
    local OPT_DESC=${1}
    echo ${OPT_DESC} | sed -e "s/\([a-zA-Z]\) [A-Z_]\+/\1:/g" -e "s/\[[^[]*\]//g" -e "s/[][ -]//g"
}

function usage {
    printf "Usage:\n\t%s\n" "${0} ${OPT_DESC}"
    exit 10
}

然后,您可以像这样使用它:

#!/bin/bash
#
# [ and ] defines optional arguments
#

# location to getopts.sh file
source ./getopt.sh
USAGE="-u USER -d DATABASE -p PASS -s SID [ -a START_DATE_TIME ]"
parse_options "${USAGE}" ${@}

echo ${USER}
echo ${START_DATE_TIME}

旧答案:

我最近需要使用通用方法。我遇到了这个解决方案:

#!/bin/bash
# Option Description:
# -------------------
#
# Option description is based on getopts bash builtin. The description adds a variable name feature to be used
# on future checks for required or optional values.
# The option description adds "=>VARIABLE_NAME" string. Variable name should be UPPERCASE. Valid characters
# are [A-Z_]*.
#
# A option description example:
#   OPT_DESC="a:=>A_VARIABLE|b:=>B_VARIABLE|c=>C_VARIABLE"
#
# -a option will require a value (the colon means that) and should be saved in variable A_VARIABLE.
# "|" is used to separate options description.
# -b option rule applies the same as -a.
# -c option doesn't require a value (the colon absense means that) and its existence should be set in C_VARIABLE
#
#   ~$ echo get_options ${OPT_DESC}
#   a:b:c
#   ~$
#


# Required options 
REQUIRED_DESC="a:=>REQ_A_VAR_VALUE|B:=>REQ_B_VAR_VALUE|c=>REQ_C_VAR_FLAG"

# Optional options (duh)
OPTIONAL_DESC="P:=>OPT_P_VAR_VALUE|r=>OPT_R_VAR_FLAG"

function usage {
    IFS="|"
    printf "%s" ${0}
    for i in ${REQUIRED_DESC};
    do
        VARNAME=$(echo $i | sed -e "s/.*=>//g")
    printf " %s" "-${i:0:1} $VARNAME"
    done

    for i in ${OPTIONAL_DESC};
    do
        VARNAME=$(echo $i | sed -e "s/.*=>//g")
        printf " %s" "[-${i:0:1} $VARNAME]"
    done
    printf "\n"
    unset IFS
    exit
}

# Auxiliary function that returns options characters to be passed
# into 'getopts' from a option description.
# Arguments:
#   $1: The options description (SEE TOP)
#
# Example:
#   OPT_DESC="h:=>H_VAR|f:=>F_VAR|P=>P_VAR|W=>W_VAR"
#   OPTIONS=$(get_options ${OPT_DESC})
#   echo "${OPTIONS}"
#
# Output:
#   "h:f:PW"
function get_options {
    echo ${1} | sed -e "s/\([a-zA-Z]\:\?\)=>[A-Z_]*|\?/\1/g"
}

# Auxiliary function that returns all variable names separated by '|'
# Arguments:
#       $1: The options description (SEE TOP)
#
# Example:
#       OPT_DESC="h:=>H_VAR|f:=>F_VAR|P=>P_VAR|W=>W_VAR"
#       VARNAMES=$(get_values ${OPT_DESC})
#       echo "${VARNAMES}"
#
# Output:
#       "H_VAR|F_VAR|P_VAR|W_VAR"
function get_variables {
    echo ${1} | sed -e "s/[a-zA-Z]\:\?=>\([^|]*\)/\1/g"
}

# Auxiliary function that returns the variable name based on the
# option passed by.
# Arguments:
#   $1: The options description (SEE TOP)
#   $2: The option which the variable name wants to be retrieved
#
# Example:
#   OPT_DESC="h:=>H_VAR|f:=>F_VAR|P=>P_VAR|W=>W_VAR"
#   H_VAR=$(get_variable_name ${OPT_DESC} "h")
#   echo "${H_VAR}"
#
# Output:
#   "H_VAR"
function get_variable_name {
    VAR=$(echo ${1} | sed -e "s/.*${2}\:\?=>\([^|]*\).*/\1/g")
    if [[ ${VAR} == ${1} ]]; then
        echo ""
    else
        echo ${VAR}
    fi
}

# Gets the required options from the required description
REQUIRED=$(get_options ${REQUIRED_DESC})

# Gets the optional options (duh) from the optional description
OPTIONAL=$(get_options ${OPTIONAL_DESC})

# or... $(get_options "${OPTIONAL_DESC}|${REQUIRED_DESC}")

# The colon at starts instructs getopts to remain silent
while getopts ":${REQUIRED}${OPTIONAL}" OPTION
do
    [[ ${OPTION} == ":" ]] && usage
    VAR=$(get_variable_name "${REQUIRED_DESC}|${OPTIONAL_DESC}" ${OPTION})
    [[ -n ${VAR} ]] && eval "$VAR=${OPTARG}"
done

shift $(($OPTIND - 1))

# Checks for required options. Report an error and exits if
# required options are missing.

# Using function version ...
VARS=$(get_variables ${REQUIRED_DESC})
IFS="|"
for VARNAME in $VARS;
do
    [[ -v ${VARNAME} ]] || usage
done
unset IFS

# ... or using IFS Version (no function)
OLDIFS=${IFS}
IFS="|"
for i in ${REQUIRED_DESC};
do
    VARNAME=$(echo $i | sed -e "s/.*=>//g")
    [[ -v ${VARNAME} ]] || usage
    printf "%s %s %s\n" "-${i:0:1}" "${!VARNAME:=present}" "${VARNAME}"
done
IFS=${OLDIFS}

我没有对此进行粗略的测试,因此我可能在其中存在一些错误。


1
如果要getopts在函数中使用,请添加local OPTIND OPTARG至函数
glenn jackman

@glennjackman实际上,它更像是一种sed方法,而不是使用getopts
Sebastian

8

POSIX 7示例

还值得检查标准中的示例:http : //pubs.opengroup.org/onlinepubs/9699919799/utilities/getopts.html

aflag=
bflag=
while getopts ab: name
do
    case $name in
    a)    aflag=1;;
    b)    bflag=1
          bval="$OPTARG";;
    ?)   printf "Usage: %s: [-a] [-b value] args\n" $0
          exit 2;;
    esac
done
if [ ! -z "$aflag" ]; then
    printf "Option -a specified\n"
fi
if [ ! -z "$bflag" ]; then
    printf 'Option -b "%s" specified\n' "$bval"
fi
shift $(($OPTIND - 1))
printf "Remaining arguments are: %s\n" "$*"

然后我们可以尝试一下:

$ sh a.sh
Remaining arguments are: 
$ sh a.sh -a
Option -a specified
Remaining arguments are: 
$ sh a.sh -b
No arg for -b option
Usage: a.sh: [-a] [-b value] args
$ sh a.sh -b myval
Option -b "myval" specified
Remaining arguments are: 
$ sh a.sh -a -b myval
Option -a specified
Option -b "myval" specified
Remaining arguments are: 
$ sh a.sh remain
Remaining arguments are: remain
$ sh a.sh -- -a remain
Remaining arguments are: -a remain

在Ubuntu 17.10中经过测试的sh是破折号0.5.8。


0

“ getops”和“ getopt”非常有限。虽然建议根本不要使用“ getopt”,但它确实提供了很多选择。其中,“ getopts”仅允许使用单个字符选项,例如“ -a”,“-b”。使用其中任何一个时,都有一些其他缺点。

所以我写了一个小脚本来代替“ getopts”和“ getopt”。这是一个开始,可能会有很多改进。

更新08-04-2020:我添加了对连字符的支持,例如“ --package-name”。

用法:“ ./ script.sh软件包安装-软件包“带空格的名称” --build --archive”

# Example:
# parseArguments "${@}"
# echo "${ARG_0}" -> package
# echo "${ARG_1}" -> install
# echo "${ARG_PACKAGE}" -> "name with space"
# echo "${ARG_BUILD}" -> 1 (true)
# echo "${ARG_ARCHIVE}" -> 1 (true)
function parseArguments() {
  PREVIOUS_ITEM=''
  COUNT=0
  for CURRENT_ITEM in "${@}"
  do
    if [[ ${CURRENT_ITEM} == "--"* ]]; then
      printf -v "ARG_$(formatArgument "${CURRENT_ITEM}")" "%s" "1" # could set this to empty string and check with [ -z "${ARG_ITEM-x}" ] if it's set, but empty.
    else
      if [[ $PREVIOUS_ITEM == "--"* ]]; then
        printf -v "ARG_$(formatArgument "${PREVIOUS_ITEM}")" "%s" "${CURRENT_ITEM}"
      else
        printf -v "ARG_${COUNT}" "%s" "${CURRENT_ITEM}"
      fi
    fi

    PREVIOUS_ITEM="${CURRENT_ITEM}"
    (( COUNT++ ))
  done
}

# Format argument.
function formatArgument() {
  ARGUMENT="${1^^}" # Capitalize.
  ARGUMENT="${ARGUMENT/--/}" # Remove "--".
  ARGUMENT="${ARGUMENT//-/_}" # Replace "-" with "_".
  echo "${ARGUMENT}"
}
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.