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

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

Is it normal that my co-workers at a fitness company criticize my food choices?

Official degrees of earth’s rotation per day

Custom alignment for GeoMarkers

Do the common programs (for example: "ls", "cat") in Linux and BSD come from the same source code?

Adventure Game (text based) in C++

How can we have a quark condensate without a quark potential?

Is there a place to find the pricing for things not mentioned in the PHB? (non-magical)

What is the relationship between relativity and the Doppler effect?

Does multi-classing into Fighter give you heavy armor proficiency?

Math equation in non italic font

ERC721: How to get the owned tokens of an address

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

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

How are passwords stolen from companies if they only store hashes?

Fastest way to pop N items from a large dict

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

Professor being mistaken for a grad student

What did “the good wine” (τὸν καλὸν οἶνον) mean in John 2:10?

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

When to use a slotted vs. solid turner?

Non-trivial topology where only open sets are closed

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?

About the actual radiative impact of greenhouse gas emission over time



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 4 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

                    How should I use the fbox command correctly to avoid producing a Bad Box message?How to put a long piece of text in a box?How to specify height and width of fboxIs there an arrayrulecolor-like command to change the rule color of fbox?What is the command to highlight bad boxes in pdf?Why does fbox sometimes place the box *over* the graphic image?how to put the text in the boxHow to create command for a box where text inside the box can automatically adjust?how can I make an fbox like command with certain color, shape and width of border?how to use fbox in align modeFbox increase the spacing between the box and it content (inner margin)how to change the box height of an equationWhat is the use of the hbox in a newcommand command?

                    Doxepinum Nexus interni Notae | Tabula navigationis3158DB01142WHOa682390"Structural Analysis of the Histamine H1 Receptor""Transdermal and Topical Drug Administration in the Treatment of Pain""Antidepressants as antipruritic agents: A review"

                    inputenc: Unicode character … not set up for use with LaTeX The Next CEO of Stack OverflowEntering Unicode characters in LaTeXHow to solve the `Package inputenc Error: Unicode char not set up for use with LaTeX` problem?solve “Unicode char is not set up for use with LaTeX” without special handling of every new interesting UTF-8 characterPackage inputenc Error: Unicode character ² (U+B2)(inputenc) not set up for use with LaTeX. acroI2C[I²C]package inputenc error unicode char (u + 190) not set up for use with latexPackage inputenc Error: Unicode char u8:′ not set up for use with LaTeX. 3′inputenc Error: Unicode char u8: not set up for use with LaTeX with G-BriefPackage Inputenc Error: Unicode char u8: not set up for use with LaTeXPackage inputenc Error: Unicode char ́ (U+301)(inputenc) not set up for use with LaTeX. includePackage inputenc Error: Unicode char ̂ (U+302)(inputenc) not set up for use with LaTeX. … $widehatleft (OA,AA' right )$Package inputenc Error: Unicode char â„¡ (U+2121)(inputenc) not set up for use with LaTeX. printbibliography[heading=bibintoc]Package inputenc Error: Unicode char − (U+2212)(inputenc) not set up for use with LaTeXPackage inputenc Error: Unicode character α (U+3B1) not set up for use with LaTeXPackage inputenc Error: Unicode characterError: ! Package inputenc Error: Unicode char ⊘ (U+2298)(inputenc) not set up for use with LaTeX