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

How difficult is it to simply disable/disengage the MCAS on Boeing 737 Max 8 & 9 Aircraft?

What are substitutions for coconut in curry?

et qui - how do you really understand that kind of phraseology?

Brexit - No Deal Rejection

Professor being mistaken for a grad student

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

Can I use USB data pins as a power source?

What is the relationship between relativity and the Doppler effect?

How do I hide Chekhov's Gun?

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

What is the significance behind "40 days" that often appears in the Bible?

Explaining pyrokinesis powers

How to make healing in an exploration game interesting

Meme-controlled people

How to pronounce "I ♥ Huckabees"?

I got the following comment from a reputed math journal. What does it mean?

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

Why do passenger jet manufacturers design their planes with stall prevention systems?

Python if-else code style for reduced code for rounding floats

Have the tides ever turned twice on any open problem?

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

What is a ^ b and (a & b) << 1?

Is there a hypothetical scenario that would make Earth uninhabitable for humans, but not for (the majority of) other animals?

Adventure Game (text based) in C++



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

                    Are there any AGPL-style licences that require source code modifications to be public? Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Force derivative works to be publicAre there any GPL like licenses for Apple App Store?Do you violate the GPL if you provide source code that cannot be compiled?GPL - is it distribution to use libraries in an appliance loaned to customers?Distributing App for free which uses GPL'ed codeModifications of server software under GPL, with web/CLI interfaceDoes using an AGPLv3-licensed library prevent me from dual-licensing my own source code?Can I publish only select code under GPLv3 from a private project?Is there published precedent regarding the scope of covered work that uses AGPL software?If MIT licensed code links to GPL licensed code what should be the license of the resulting binary program?If I use a public API endpoint that has its source code licensed under AGPL in my app, do I need to disclose my source?

                    2013 GY136 Descoberta | Órbita | Referências Menu de navegação«List Of Centaurs and Scattered-Disk Objects»«List of Known Trans-Neptunian Objects»

                    Button changing it's text & action. Good or terrible? The 2019 Stack Overflow Developer Survey Results Are Inchanging text on user mouseoverShould certain functions be “hard to find” for powerusers to discover?Custom liking function - do I need user login?Using different checkbox style for different checkbox behaviorBest Practices: Save and Exit in Software UIInteraction with remote validated formMore efficient UI to progress the user through a complicated process?Designing a popup notice for a gameShould bulk-editing functions be hidden until a table row is selected, or is there a better solution?Is it bad practice to disable (replace) the context menu?