Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6770549
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T15:19:32+00:00 2026-05-26T15:19:32+00:00

I have a bash script where you can specify options with –option parameter: if

  • 0

I have a bash script where you can specify options with “–option parameter”:

if [ ${1:0:2} != '--' ] ; then 
    echo -e "Unrecognized option: $1\n$requestHelpMessage"; exit 1;
fi
if [ ! $2 ];
    then echo -e "Expected parameter for $1\n$requestHelpMessage"; exit 1;
fi
case ${1:2} in
    branch) # do something with $2 here
    batch) # do something with $2 here
    version) # do something with $2 here
    *) # you get the idea
esac

And I want to extend it to be able to handle “–option=parameter” as well. Is there an easy way to split over “=” without special-casing each one?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T15:19:32+00:00Added an answer on May 26, 2026 at 3:19 pm

    Instead of using getopt or making your own setup, try using “getopt“. It supports both long (word) and short (character) arguments.

    Here’s an example of it in use:

    get_inputs () {
        set -- $( getopt -u -l class:,desc:,force,host:,help,verbose "c:d:fh:v?" "$@" )
    
        while [ $# -gt 0 ]; do 
            case "$1" in
                -c|--class)
                    CLASS=$2
                    shift
                    ;;
                -d|--desc)  
                    DESCR=$2
                    shift
                    ;;
                -f|--force)
                    FORCE=1
                    ;;
                -h|--host)
                    HOST=$2
                    shift
                    ;;
                -v|--verbose)
                    VERBOSE=1
                    ;;
                --help)
                    usage
                    exit
                    ;;
                *)
                    break
                    ;;
            esac
            shift
        done
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Possible Duplicate: Automatic exit from bash shell script on error How can I have
Can you use the bash getopts function twice in the same script? I have
I have a bash script which is getting options (using getopts). Let say they
I have a strange problem with BASH script which I can't figure out. I
I have bash script where i have echo before every command showing what is
I have a bash script which calls another bash script, like so: #!/bin/bash echo
I have bash script that takes in a couple of arguments tests then and
I have a bash script in which i check the exit code of a
I have a bash script that creates a Subversion patch file for the current
I have a bash script that runs a simulation program written in Fortran 90,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.