Ygtjki

In predicate logic, does existential quantification (∃) include universal quantification (∀), i.e. can 'some' imply 'all'?

ListPlot join points by nearest neighbor rather than order

Is there a program I can run on the C64 to speed up booting of a game?

How come Sam didn't become Lord of Horn Hill?

At the end of Thor: Ragnarok why don't the Asgardians turn and head for the Bifrost as per their original plan?

Should I discuss the type of campaign with my players?

What's the purpose of writing one's academic biography in the third person?

Can I cast Passwall to drop an enemy into a 20-foot pit?

What does this icon in iOS Stardew Valley mean?

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?

Single word antonym of "flightless"

Why are Kinder Surprise Eggs illegal in the USA?

Why is my conclusion inconsistent with the van't Hoff equation?

How to run gsettings for another user Ubuntu 18.04.2 LTS

How to tell that you are a giant?

Can a USB port passively 'listen only'?

What does the word "veer" mean here?

Why was the term "discrete" used in discrete logarithm?

Why didn't this character "real die" when they blew their stack out in Altered Carbon?

How to react to hostile behavior from a senior developer?

51k Euros annually for a family of 4 in Berlin: Is it enough?

How to call a function with default parameter through a pointer to function that is the return of another function?

Should I use a zero-interest credit card for a large one-time purchase?

How do I pass long-style command line options to a bash script using getopt?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

0

I have this script that I have cobbled together from bits of lore I've gleaned from googling:

#!/usr/bin/env bash

usage() bar.com

main() 
 if [[ $# -eq 0 ]]; then
 usage
 exit 1
 fi

OPTIONS=$(getopt -o '' -l help,host,accountId -- "$@")

eval set -- "$OPTIONS"

while true
do
 case $1 in
 -help) usage
 exit 0
 ;;
 -accountId) ACCOUNTID=$2; shift 2;;
 -host) HOST=$2 shift 2;;
 --) shift ; break ;;
 esac
done

echo host: $HOST, accountId: $ACCOUNTID



main "$@"

Here's what it outputs:

$ . test.sh -help
host: , accountId:

$ . test.sh -host foo.com -accountId 001123456789
host: , accountId:

I'm a bash scripting newbie. What have I done wrong?

bash shell-script options getopts

share|improve this question

asked Apr 12 at 15:44

braveterrybraveterry

1012

New contributor

braveterry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  A long option is usually preceded by --, as in --accountId.
  
  – Kusalananda♦
  Apr 12 at 15:57
  

  
  
  
  

add a comment | 

0

0

I have this script that I have cobbled together from bits of lore I've gleaned from googling:

#!/usr/bin/env bash

usage() bar.com

main() 
 if [[ $# -eq 0 ]]; then
 usage
 exit 1
 fi

OPTIONS=$(getopt -o '' -l help,host,accountId -- "$@")

eval set -- "$OPTIONS"

while true
do
 case $1 in
 -help) usage
 exit 0
 ;;
 -accountId) ACCOUNTID=$2; shift 2;;
 -host) HOST=$2 shift 2;;
 --) shift ; break ;;
 esac
done

echo host: $HOST, accountId: $ACCOUNTID



main "$@"

Here's what it outputs:

$ . test.sh -help
host: , accountId:

$ . test.sh -host foo.com -accountId 001123456789
host: , accountId:

I'm a bash scripting newbie. What have I done wrong?

bash shell-script options getopts

share|improve this question

asked Apr 12 at 15:44

braveterrybraveterry

1012

New contributor

braveterry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  A long option is usually preceded by --, as in --accountId.
  
  – Kusalananda♦
  Apr 12 at 15:57
  

  
  
  
  

add a comment | 

I have this script that I have cobbled together from bits of lore I've gleaned from googling:

#!/usr/bin/env bash

usage() bar.com

main() 
 if [[ $# -eq 0 ]]; then
 usage
 exit 1
 fi

OPTIONS=$(getopt -o '' -l help,host,accountId -- "$@")

eval set -- "$OPTIONS"

while true
do
 case $1 in
 -help) usage
 exit 0
 ;;
 -accountId) ACCOUNTID=$2; shift 2;;
 -host) HOST=$2 shift 2;;
 --) shift ; break ;;
 esac
done

echo host: $HOST, accountId: $ACCOUNTID



main "$@"

Here's what it outputs:

$ . test.sh -help
host: , accountId:

$ . test.sh -host foo.com -accountId 001123456789
host: , accountId:

I'm a bash scripting newbie. What have I done wrong?

bash shell-script options getopts

share|improve this question

asked Apr 12 at 15:44

braveterrybraveterry

1012

New contributor

braveterry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

#!/usr/bin/env bash

usage() bar.com

main() 
 if [[ $# -eq 0 ]]; then
 usage
 exit 1
 fi

OPTIONS=$(getopt -o '' -l help,host,accountId -- "$@")

eval set -- "$OPTIONS"

while true
do
 case $1 in
 -help) usage
 exit 0
 ;;
 -accountId) ACCOUNTID=$2; shift 2;;
 -host) HOST=$2 shift 2;;
 --) shift ; break ;;
 esac
done

echo host: $HOST, accountId: $ACCOUNTID



main "$@"

$ . test.sh -help
host: , accountId:

$ . test.sh -host foo.com -accountId 001123456789
host: , accountId:

share|improve this question

asked Apr 12 at 15:44

braveterrybraveterry

1012

New contributor

braveterry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked Apr 12 at 15:44

braveterrybraveterry

1012

New contributor

braveterry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked Apr 12 at 15:44

braveterrybraveterry

1012

New contributor

braveterry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked Apr 12 at 15:44

braveterrybraveterry

1012

1 Answer
1

active

oldest

votes

2

Minor bug, there should be a ; after the HOST=$2

If you want to use a single dash in front of long options, you can add the -a option to getopt.

Also as the host and accountId have required options, they should be followed by a :

OPTIONS=$( getopt -a -o '' -l help,host:,accountId: -- "$@" )

(camelCase isn't the best for options, how about just accountid instead of accountId)

And I generally prefer to give both long and short options, so would use:

OPTIONS=$( getopt -a -o 'h:a:' -l help,host:,accountId: -- "$@" )

and

-a|--accountId) ACCOUNTID=$2; shift 2;;
-h|--host) HOST=$2; shift 2;;

You should also check the result code from getopt, if the options are wrong you don't want to continue:

So after the OPTIONS=$(... line add the following:

if [[ $? -ne 0 ]] ; then
 usage ; exit 1
fi

And on a minor aside, if the usage is being displayed, you probably always want to exit, so why not put the exit 1 at the end of usage, then you could use:

[[ $# -eq 0 ]] && usage
...
[[ $? -ne 0 ]] && usage
...
--help) usage;;

share|improve this answer

edited Apr 12 at 18:10

answered Apr 12 at 17:43

XrXcaXrXca

913

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

braveterry is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f512127%2fhow-do-i-pass-long-style-command-line-options-to-a-bash-script-using-getopt%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

2

Minor bug, there should be a ; after the HOST=$2

If you want to use a single dash in front of long options, you can add the -a option to getopt.

Also as the host and accountId have required options, they should be followed by a :

OPTIONS=$( getopt -a -o '' -l help,host:,accountId: -- "$@" )

(camelCase isn't the best for options, how about just accountid instead of accountId)

And I generally prefer to give both long and short options, so would use:

OPTIONS=$( getopt -a -o 'h:a:' -l help,host:,accountId: -- "$@" )

and

-a|--accountId) ACCOUNTID=$2; shift 2;;
-h|--host) HOST=$2; shift 2;;

You should also check the result code from getopt, if the options are wrong you don't want to continue:

So after the OPTIONS=$(... line add the following:

if [[ $? -ne 0 ]] ; then
 usage ; exit 1
fi

And on a minor aside, if the usage is being displayed, you probably always want to exit, so why not put the exit 1 at the end of usage, then you could use:

[[ $# -eq 0 ]] && usage
...
[[ $? -ne 0 ]] && usage
...
--help) usage;;

share|improve this answer

edited Apr 12 at 18:10

answered Apr 12 at 17:43

XrXcaXrXca

913

add a comment | 

2

Minor bug, there should be a ; after the HOST=$2

If you want to use a single dash in front of long options, you can add the -a option to getopt.

Also as the host and accountId have required options, they should be followed by a :

OPTIONS=$( getopt -a -o '' -l help,host:,accountId: -- "$@" )

(camelCase isn't the best for options, how about just accountid instead of accountId)

And I generally prefer to give both long and short options, so would use:

OPTIONS=$( getopt -a -o 'h:a:' -l help,host:,accountId: -- "$@" )

and

-a|--accountId) ACCOUNTID=$2; shift 2;;
-h|--host) HOST=$2; shift 2;;

You should also check the result code from getopt, if the options are wrong you don't want to continue:

So after the OPTIONS=$(... line add the following:

if [[ $? -ne 0 ]] ; then
 usage ; exit 1
fi

And on a minor aside, if the usage is being displayed, you probably always want to exit, so why not put the exit 1 at the end of usage, then you could use:

[[ $# -eq 0 ]] && usage
...
[[ $? -ne 0 ]] && usage
...
--help) usage;;

share|improve this answer

edited Apr 12 at 18:10

answered Apr 12 at 17:43

XrXcaXrXca

913

add a comment | 

Minor bug, there should be a ; after the HOST=$2

If you want to use a single dash in front of long options, you can add the -a option to getopt.

Also as the host and accountId have required options, they should be followed by a :

OPTIONS=$( getopt -a -o '' -l help,host:,accountId: -- "$@" )

(camelCase isn't the best for options, how about just accountid instead of accountId)

And I generally prefer to give both long and short options, so would use:

OPTIONS=$( getopt -a -o 'h:a:' -l help,host:,accountId: -- "$@" )

and

-a|--accountId) ACCOUNTID=$2; shift 2;;
-h|--host) HOST=$2; shift 2;;

You should also check the result code from getopt, if the options are wrong you don't want to continue:

So after the OPTIONS=$(... line add the following:

if [[ $? -ne 0 ]] ; then
 usage ; exit 1
fi

And on a minor aside, if the usage is being displayed, you probably always want to exit, so why not put the exit 1 at the end of usage, then you could use:

[[ $# -eq 0 ]] && usage
...
[[ $? -ne 0 ]] && usage
...
--help) usage;;

share|improve this answer

edited Apr 12 at 18:10

answered Apr 12 at 17:43

XrXcaXrXca

913

OPTIONS=$( getopt -a -o '' -l help,host:,accountId: -- "$@" )

OPTIONS=$( getopt -a -o 'h:a:' -l help,host:,accountId: -- "$@" )

-a|--accountId) ACCOUNTID=$2; shift 2;;
-h|--host) HOST=$2; shift 2;;

if [[ $? -ne 0 ]] ; then
 usage ; exit 1
fi

[[ $# -eq 0 ]] && usage
...
[[ $? -ne 0 ]] && usage
...
--help) usage;;

share|improve this answer

edited Apr 12 at 18:10

answered Apr 12 at 17:43

XrXcaXrXca

913

answered Apr 12 at 17:43

XrXcaXrXca

913

answered Apr 12 at 17:43

XrXcaXrXca

913