Does .bashrc contain syntax errors?What does the 'rc' in `.bashrc`, etc. mean?source .bashrc doesn't workNo...

Recruiter wants very extensive technical details about all of my previous work

If I can solve Sudoku, can I solve the Travelling Salesman Problem (TSP)? If so, how?

Print a physical multiplication table

Can I use USB data pins as a power source?

Why does overlay work only on the first tcolorbox?

Simplify an interface for flexibly applying rules to periods of time

Why Choose Less Effective Armour Types?

I am confused as to how the inverse of a certain function is found.

Why is a white electrical wire connected to 2 black wires?

Are all passive ability checks floors for active ability checks?

A single argument pattern definition applies to multiple-argument patterns?

Employee lack of ownership

What options are left, if Britain cannot decide?

Is it true that good novels will automatically sell themselves on Amazon (and so on) and there is no need for one to waste time promoting?

Have the tides ever turned twice on any open problem?

Custom alignment for GeoMarkers

As a new Ubuntu desktop 18.04 LTS user, do I need to use ufw for a firewall or is iptables sufficient?

Different outputs for `w`, `who`, `whoami` and `id`

Happy pi day, everyone!

Does .bashrc contain syntax errors?

A diagram about partial derivatives of f(x,y)

If I am holding an item before I cast Blink, will it move with me through the Ethereal Plane?

How could an airship be repaired midflight?

Math equation in non italic font



Does .bashrc contain syntax errors?


What does the 'rc' in `.bashrc`, etc. mean?source .bashrc doesn't workNo bashrc file in my home directoryWhat does . .bashrc actually do?BASH string manipulation, syntax errorsline 63: syntax error near unexpected token `;' in bashrcsyntax error near unexpected token `(' bashWhat does bashrc PS1 check [ “$PS1” = “\s-\v\$ ” ] mean?Linux: bashrc. How to load bashrc content from another file?Bashrc unexpected EOF Error













1















In the Ubuntu 18.04 LT .bashrc file there is the following:



# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac


Isn't xterm-color) an instance of unbalanced parentheses? And why does the line end with two semicolons?



To be clear, this is not something I wrote. It's in the virgin file, not edited by me.



If there are syntax errors, to whom should I report this?










share|improve this question



























    1















    In the Ubuntu 18.04 LT .bashrc file there is the following:



    # set a fancy prompt (non-color, unless we know we "want" color)
    case "$TERM" in
    xterm-color) color_prompt=yes;;
    esac


    Isn't xterm-color) an instance of unbalanced parentheses? And why does the line end with two semicolons?



    To be clear, this is not something I wrote. It's in the virgin file, not edited by me.



    If there are syntax errors, to whom should I report this?










    share|improve this question

























      1












      1








      1








      In the Ubuntu 18.04 LT .bashrc file there is the following:



      # set a fancy prompt (non-color, unless we know we "want" color)
      case "$TERM" in
      xterm-color) color_prompt=yes;;
      esac


      Isn't xterm-color) an instance of unbalanced parentheses? And why does the line end with two semicolons?



      To be clear, this is not something I wrote. It's in the virgin file, not edited by me.



      If there are syntax errors, to whom should I report this?










      share|improve this question














      In the Ubuntu 18.04 LT .bashrc file there is the following:



      # set a fancy prompt (non-color, unless we know we "want" color)
      case "$TERM" in
      xterm-color) color_prompt=yes;;
      esac


      Isn't xterm-color) an instance of unbalanced parentheses? And why does the line end with two semicolons?



      To be clear, this is not something I wrote. It's in the virgin file, not edited by me.



      If there are syntax errors, to whom should I report this?







      linux ubuntu bash bashrc






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 4 hours ago









      ArgentArgent

      132




      132






















          1 Answer
          1






          active

          oldest

          votes


















          3














          This is the standard, correct syntax for a bash case statement(known abstractly as a switch statement in general programming), albeit perhaps an odd syntax when compared to Python, Java, or other languages.



          From The Linux Documentation Project:




          Nested if statements might be nice, but as soon as you are confronted
          with a couple of different possible actions to take, they tend to
          confuse. For the more complex conditionals, use the case syntax:



          case EXPRESSION in CASE1) COMMAND-LIST;; CASE2) COMMAND-LIST;; ... CASEN) COMMAND-LIST;; esac






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2fsuperuser.com%2fquestions%2f1414684%2fdoes-bashrc-contain-syntax-errors%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









            3














            This is the standard, correct syntax for a bash case statement(known abstractly as a switch statement in general programming), albeit perhaps an odd syntax when compared to Python, Java, or other languages.



            From The Linux Documentation Project:




            Nested if statements might be nice, but as soon as you are confronted
            with a couple of different possible actions to take, they tend to
            confuse. For the more complex conditionals, use the case syntax:



            case EXPRESSION in CASE1) COMMAND-LIST;; CASE2) COMMAND-LIST;; ... CASEN) COMMAND-LIST;; esac






            share|improve this answer






























              3














              This is the standard, correct syntax for a bash case statement(known abstractly as a switch statement in general programming), albeit perhaps an odd syntax when compared to Python, Java, or other languages.



              From The Linux Documentation Project:




              Nested if statements might be nice, but as soon as you are confronted
              with a couple of different possible actions to take, they tend to
              confuse. For the more complex conditionals, use the case syntax:



              case EXPRESSION in CASE1) COMMAND-LIST;; CASE2) COMMAND-LIST;; ... CASEN) COMMAND-LIST;; esac






              share|improve this answer




























                3












                3








                3







                This is the standard, correct syntax for a bash case statement(known abstractly as a switch statement in general programming), albeit perhaps an odd syntax when compared to Python, Java, or other languages.



                From The Linux Documentation Project:




                Nested if statements might be nice, but as soon as you are confronted
                with a couple of different possible actions to take, they tend to
                confuse. For the more complex conditionals, use the case syntax:



                case EXPRESSION in CASE1) COMMAND-LIST;; CASE2) COMMAND-LIST;; ... CASEN) COMMAND-LIST;; esac






                share|improve this answer















                This is the standard, correct syntax for a bash case statement(known abstractly as a switch statement in general programming), albeit perhaps an odd syntax when compared to Python, Java, or other languages.



                From The Linux Documentation Project:




                Nested if statements might be nice, but as soon as you are confronted
                with a couple of different possible actions to take, they tend to
                confuse. For the more complex conditionals, use the case syntax:



                case EXPRESSION in CASE1) COMMAND-LIST;; CASE2) COMMAND-LIST;; ... CASEN) COMMAND-LIST;; esac







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 3 hours ago

























                answered 3 hours ago









                baelxbaelx

                1,478616




                1,478616






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1414684%2fdoes-bashrc-contain-syntax-errors%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

                    “%fieldName is a required field.”, in Magento2 REST API Call for GET Method Type The Next...

                    How to change City field to a dropdown in Checkout step Magento 2Magento 2 : How to change UI field(s)...

                    變成蝙蝠會怎樣? 參考資料 外部連結 导航菜单Thomas Nagel, "What is it like to be a...