getopts does not seem to work











up vote
1
down vote

favorite












I am trying to run the following script using getopts to parse the options but it does not seem to work:



#!/bin/bash
set -x
echo $@
while getopts "rf" opt
do
case "${opt}" in
r)
ropt=${OPTARG}
;;
f)
fopt=${OPTARG}
;;
esac
done

shift $((OPTIND -1))

echo $fopt $ropt


The output I get is:



$ ./myscript.sh -f opt2 -r opt1
+ echo -f opt2 -r opt1
-f opt2 -r opt1
+ getopts rf opt
+ case "${opt}" in
+ fopt=
+ getopts rf opt
+ shift 1
+ echo

+ set +x


Do you have any ideas on what am I doing wrong?










share|improve this question




























    up vote
    1
    down vote

    favorite












    I am trying to run the following script using getopts to parse the options but it does not seem to work:



    #!/bin/bash
    set -x
    echo $@
    while getopts "rf" opt
    do
    case "${opt}" in
    r)
    ropt=${OPTARG}
    ;;
    f)
    fopt=${OPTARG}
    ;;
    esac
    done

    shift $((OPTIND -1))

    echo $fopt $ropt


    The output I get is:



    $ ./myscript.sh -f opt2 -r opt1
    + echo -f opt2 -r opt1
    -f opt2 -r opt1
    + getopts rf opt
    + case "${opt}" in
    + fopt=
    + getopts rf opt
    + shift 1
    + echo

    + set +x


    Do you have any ideas on what am I doing wrong?










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I am trying to run the following script using getopts to parse the options but it does not seem to work:



      #!/bin/bash
      set -x
      echo $@
      while getopts "rf" opt
      do
      case "${opt}" in
      r)
      ropt=${OPTARG}
      ;;
      f)
      fopt=${OPTARG}
      ;;
      esac
      done

      shift $((OPTIND -1))

      echo $fopt $ropt


      The output I get is:



      $ ./myscript.sh -f opt2 -r opt1
      + echo -f opt2 -r opt1
      -f opt2 -r opt1
      + getopts rf opt
      + case "${opt}" in
      + fopt=
      + getopts rf opt
      + shift 1
      + echo

      + set +x


      Do you have any ideas on what am I doing wrong?










      share|improve this question















      I am trying to run the following script using getopts to parse the options but it does not seem to work:



      #!/bin/bash
      set -x
      echo $@
      while getopts "rf" opt
      do
      case "${opt}" in
      r)
      ropt=${OPTARG}
      ;;
      f)
      fopt=${OPTARG}
      ;;
      esac
      done

      shift $((OPTIND -1))

      echo $fopt $ropt


      The output I get is:



      $ ./myscript.sh -f opt2 -r opt1
      + echo -f opt2 -r opt1
      -f opt2 -r opt1
      + getopts rf opt
      + case "${opt}" in
      + fopt=
      + getopts rf opt
      + shift 1
      + echo

      + set +x


      Do you have any ideas on what am I doing wrong?







      bash getopts






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 30 mins ago









      Kusalananda

      119k16223365




      119k16223365










      asked 1 hour ago









      trikelef

      14418




      14418






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          4
          down vote



          accepted










          You expect your options to take option-arguments, but you don't let getopts know about this.



          You should use



          while getopts "r:f:" opt; do ...; done


          i.e., each option that takes an argument should have : after it in the argument string to getopts.



          You'll probably also want a default case branch at the end to handle invalid options:



           *) usage >&2
          exit 1


          (the error message (about invalid option or missing option argument) will be displayed by getopts itself, usage is expected to be a function that you will have defined that prints a short help message to standard output).



          Also, don't forget to double quote all expansions, even $(( OPTIND - 1 )).



          Related to that last point:




          • When is double-quoting necessary?






          share|improve this answer























            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',
            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487548%2fgetopts-does-not-seem-to-work%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            4
            down vote



            accepted










            You expect your options to take option-arguments, but you don't let getopts know about this.



            You should use



            while getopts "r:f:" opt; do ...; done


            i.e., each option that takes an argument should have : after it in the argument string to getopts.



            You'll probably also want a default case branch at the end to handle invalid options:



             *) usage >&2
            exit 1


            (the error message (about invalid option or missing option argument) will be displayed by getopts itself, usage is expected to be a function that you will have defined that prints a short help message to standard output).



            Also, don't forget to double quote all expansions, even $(( OPTIND - 1 )).



            Related to that last point:




            • When is double-quoting necessary?






            share|improve this answer



























              up vote
              4
              down vote



              accepted










              You expect your options to take option-arguments, but you don't let getopts know about this.



              You should use



              while getopts "r:f:" opt; do ...; done


              i.e., each option that takes an argument should have : after it in the argument string to getopts.



              You'll probably also want a default case branch at the end to handle invalid options:



               *) usage >&2
              exit 1


              (the error message (about invalid option or missing option argument) will be displayed by getopts itself, usage is expected to be a function that you will have defined that prints a short help message to standard output).



              Also, don't forget to double quote all expansions, even $(( OPTIND - 1 )).



              Related to that last point:




              • When is double-quoting necessary?






              share|improve this answer

























                up vote
                4
                down vote



                accepted







                up vote
                4
                down vote



                accepted






                You expect your options to take option-arguments, but you don't let getopts know about this.



                You should use



                while getopts "r:f:" opt; do ...; done


                i.e., each option that takes an argument should have : after it in the argument string to getopts.



                You'll probably also want a default case branch at the end to handle invalid options:



                 *) usage >&2
                exit 1


                (the error message (about invalid option or missing option argument) will be displayed by getopts itself, usage is expected to be a function that you will have defined that prints a short help message to standard output).



                Also, don't forget to double quote all expansions, even $(( OPTIND - 1 )).



                Related to that last point:




                • When is double-quoting necessary?






                share|improve this answer














                You expect your options to take option-arguments, but you don't let getopts know about this.



                You should use



                while getopts "r:f:" opt; do ...; done


                i.e., each option that takes an argument should have : after it in the argument string to getopts.



                You'll probably also want a default case branch at the end to handle invalid options:



                 *) usage >&2
                exit 1


                (the error message (about invalid option or missing option argument) will be displayed by getopts itself, usage is expected to be a function that you will have defined that prints a short help message to standard output).



                Also, don't forget to double quote all expansions, even $(( OPTIND - 1 )).



                Related to that last point:




                • When is double-quoting necessary?







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 17 mins ago

























                answered 1 hour ago









                Kusalananda

                119k16223365




                119k16223365






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487548%2fgetopts-does-not-seem-to-work%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    What visual should I use to simply compare current year value vs last year in Power BI desktop

                    Alexandru Averescu

                    Trompette piccolo