order parameters in getopts

Question

I have to write very simple script. It should take 2 args -h and -q. Both are optional, -h can be somewhere. So, -h -q should does the same action like -q -h. If I pass -a ,or -a -a -a - an error should occurs (I mean exit 1). If I pass -a -h -a -a -b.... - it should return "I couldn't recognize -a" + invoke help case. So -h has priority. Could you help me?

while getopts "hq" OPTION
do
case $OPTION in
  h)
     echo "Help here!" ;
     exit 0;
     
esac
done
shift $(($OPTIND - 1))

while getopts "hq" OPTION
do
case $OPTION in
  q) #quiet - return 0, do nothing. 
     exit 0;;
 

                   
  *) #If -a or sth
     echo "I couldn't recognize args" 
     echo "Help here" 
     exit 1
     ;;
     
esac
     
done

You need to use a single `while getopts` loop to process *all* of the options, not one for `-h` followed by one for `-q`. — Gordon Davisson, Oct 12 '20 at 20:58
Where on stack? It should probably corrected, because it will not work right (unless there's some weird situation where makes sense). — Gordon Davisson, Oct 12 '20 at 21:03
Have a look at https://stackoverflow.com/questions/192249/how-do-i-parse-command-line-arguments-in-bash/14203146#14203146 — F. Hauri - Give Up GitHub, Oct 13 '20 at 07:13

score 0 · Answer 1 · answered Oct 12 '20 at 22:15

0

This is the correct implementation:

#!/usr/bin/env bash

while getopts :hq OPTION
do  
    case $OPTION in
    h) echo "Help here!" ;
       exit 0;;
    q) echo "quiet do nothing."
       exit 0;;
    ?) echo "I couldn't recognize option [$1]" 
       exit 1;;
    esac
done
shift $((OPTIND - 1))

Note :hq and ?) to process incorrect options (-a -b ...)

answered Oct 12 '20 at 22:15

Philippe

20,025
2
23
32

You could explain, regarding SO question: *`while getopts` will **loop** over each option passed to script*... – F. Hauri - Give Up GitHub Oct 13 '20 at 07:11

order parameters in getopts

1 Answers1