“not a valid identifier” when I do “export $PATH”bash : export: `PATH:home/pi/netkit/bin:/usr/local … invalid indentifierAfter starting terminal always getting bash: export: “path” not a valid identifierbash: export: `--wait': not a valid identifierExport path with space in directory nameSetting environment variables with .bash_profile: only last export works properlyZsh: export: not valid in this contextError when exporting the result of a valid command as a bash variable“export VAR=thing && someCommand” reports “export: `&&': not a valid identifier”Can't export string variablesbash: ‘export: command not foundAfter starting terminal always getting bash: export: “path” not a valid identifierExport commands works in interactive mode, but produces error message in script

Use Mercury as quenching liquid for swords?

Create chunks from an array

How would an energy-based "projectile" blow up a spaceship?

Is "cogitate" used appropriately in "I cogitate that success relies on hard work"?

Does the US political system, in principle, allow for a no-party system?

A vote on the Brexit backstop

What is the orbit and expected lifetime of Crew Dragon trunk?

What is Tony Stark injecting into himself in Iron Man 3?

Rationale to prefer local variables over instance variables?

Should I file my taxes? No income, unemployed, but paid 2k in student loan interest

What do you call someone who likes to pick fights?

Help! My Character is too much for her story!

Short SF story. Females use stingers to implant eggs in yearfathers

Is divide-by-zero a security vulnerability?

Is this Paypal Github SDK reference really a dangerous site?

Are brahmins allowed to drink alcohol?

Was this cameo in Captain Marvel computer generated?

Why does this boat have a landing pad? (SpaceX's GO Searcher) Any plans for propulsive capsule landings?

How does a sound wave propagate?

Vector-transposing function

Where is the License file location for Identity Server in Sitecore 9.1?

Why is there an extra space when I type "ls" on the Desktop?

What is the oldest European royal house?

Is there a math expression equivalent to the conditional ternary operator?



“not a valid identifier” when I do “export $PATH”


bash : export: `PATH:home/pi/netkit/bin:/usr/local … invalid indentifierAfter starting terminal always getting bash: export: “path” not a valid identifierbash: export: `--wait': not a valid identifierExport path with space in directory nameSetting environment variables with .bash_profile: only last export works properlyZsh: export: not valid in this contextError when exporting the result of a valid command as a bash variable“export VAR=thing && someCommand” reports “export: `&&': not a valid identifier”Can't export string variablesbash: ‘export: command not foundAfter starting terminal always getting bash: export: “path” not a valid identifierExport commands works in interactive mode, but produces error message in script













34















When I run export $PATH in bash, I get the error not a valid identifier. Why?










share|improve this question



















  • 8





    In bash and other shells, $ is “value of”. You're exporting the variable PATH, not accessing its value, so it's export PATH with no $.

    – Gilles
    Jun 17 '13 at 18:10















34















When I run export $PATH in bash, I get the error not a valid identifier. Why?










share|improve this question



















  • 8





    In bash and other shells, $ is “value of”. You're exporting the variable PATH, not accessing its value, so it's export PATH with no $.

    – Gilles
    Jun 17 '13 at 18:10













34












34








34


7






When I run export $PATH in bash, I get the error not a valid identifier. Why?










share|improve this question
















When I run export $PATH in bash, I get the error not a valid identifier. Why?







bash shell environment-variables






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 7 '15 at 9:51







ThaSaleni

















asked Jun 17 '13 at 7:53









ThaSaleniThaSaleni

296135




296135







  • 8





    In bash and other shells, $ is “value of”. You're exporting the variable PATH, not accessing its value, so it's export PATH with no $.

    – Gilles
    Jun 17 '13 at 18:10












  • 8





    In bash and other shells, $ is “value of”. You're exporting the variable PATH, not accessing its value, so it's export PATH with no $.

    – Gilles
    Jun 17 '13 at 18:10







8




8





In bash and other shells, $ is “value of”. You're exporting the variable PATH, not accessing its value, so it's export PATH with no $.

– Gilles
Jun 17 '13 at 18:10





In bash and other shells, $ is “value of”. You're exporting the variable PATH, not accessing its value, so it's export PATH with no $.

– Gilles
Jun 17 '13 at 18:10










4 Answers
4






active

oldest

votes


















34














Running export $PATH will try to export a variable with a name equal to the value of $PATH (after word splitting). That is, it's equivalent to writing something like export /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin. And since /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid variable name, it fails. What you want to do is export PATH.



export (equivalent to declare -x) in Bash simply makes the variable available to subshells.



To print the value of a variable safely and readably, use printf %q "$PATH".






share|improve this answer

























  • Basically I have created some variables, JAVA_HOME, MAVEN_HOME and want to make sure that bash has properly set them, so I export $PATH to see if the path variables have been properly set to the PATH variable

    – ThaSaleni
    Jun 17 '13 at 10:04






  • 1





    This is shell dependent, not OS dependent. I would be surprised if export ever worked like that in Bash.

    – l0b0
    Jun 17 '13 at 10:04












  • Additionally, the PATH variable is already exported and does not need to be exported again.

    – Kusalananda
    Apr 14 '18 at 9:57


















16














The following command export $PATH=somePath will return not a valid identifier and that is because of the $ before the PATH variable.



solution:



export PATH=somePath






share|improve this answer






























    0














    You should use it this way:
    export PATH=$PATH:/something/bin
    Instead of:
    export $PATH=$PATH:/something/bin



    just remove the $ sign from the LHS





    share








    New contributor




    Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.



























      -1














      You probably had a need to append a $PATH to your existing PATH variable ?



      export PATH=$PATH:/something/bin





      share|improve this answer




















      • 1





        OK, this is in the same ball park as the question, but it’s out in left field.

        – G-Man
        Mar 15 '18 at 0:12










      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',
      autoActivateHeartbeat: false,
      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%2f79658%2fnot-a-valid-identifier-when-i-do-export-path%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      34














      Running export $PATH will try to export a variable with a name equal to the value of $PATH (after word splitting). That is, it's equivalent to writing something like export /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin. And since /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid variable name, it fails. What you want to do is export PATH.



      export (equivalent to declare -x) in Bash simply makes the variable available to subshells.



      To print the value of a variable safely and readably, use printf %q "$PATH".






      share|improve this answer

























      • Basically I have created some variables, JAVA_HOME, MAVEN_HOME and want to make sure that bash has properly set them, so I export $PATH to see if the path variables have been properly set to the PATH variable

        – ThaSaleni
        Jun 17 '13 at 10:04






      • 1





        This is shell dependent, not OS dependent. I would be surprised if export ever worked like that in Bash.

        – l0b0
        Jun 17 '13 at 10:04












      • Additionally, the PATH variable is already exported and does not need to be exported again.

        – Kusalananda
        Apr 14 '18 at 9:57















      34














      Running export $PATH will try to export a variable with a name equal to the value of $PATH (after word splitting). That is, it's equivalent to writing something like export /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin. And since /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid variable name, it fails. What you want to do is export PATH.



      export (equivalent to declare -x) in Bash simply makes the variable available to subshells.



      To print the value of a variable safely and readably, use printf %q "$PATH".






      share|improve this answer

























      • Basically I have created some variables, JAVA_HOME, MAVEN_HOME and want to make sure that bash has properly set them, so I export $PATH to see if the path variables have been properly set to the PATH variable

        – ThaSaleni
        Jun 17 '13 at 10:04






      • 1





        This is shell dependent, not OS dependent. I would be surprised if export ever worked like that in Bash.

        – l0b0
        Jun 17 '13 at 10:04












      • Additionally, the PATH variable is already exported and does not need to be exported again.

        – Kusalananda
        Apr 14 '18 at 9:57













      34












      34








      34







      Running export $PATH will try to export a variable with a name equal to the value of $PATH (after word splitting). That is, it's equivalent to writing something like export /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin. And since /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid variable name, it fails. What you want to do is export PATH.



      export (equivalent to declare -x) in Bash simply makes the variable available to subshells.



      To print the value of a variable safely and readably, use printf %q "$PATH".






      share|improve this answer















      Running export $PATH will try to export a variable with a name equal to the value of $PATH (after word splitting). That is, it's equivalent to writing something like export /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin. And since /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid variable name, it fails. What you want to do is export PATH.



      export (equivalent to declare -x) in Bash simply makes the variable available to subshells.



      To print the value of a variable safely and readably, use printf %q "$PATH".







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Apr 14 '18 at 20:59

























      answered Jun 17 '13 at 8:19









      l0b0l0b0

      28.4k19120248




      28.4k19120248












      • Basically I have created some variables, JAVA_HOME, MAVEN_HOME and want to make sure that bash has properly set them, so I export $PATH to see if the path variables have been properly set to the PATH variable

        – ThaSaleni
        Jun 17 '13 at 10:04






      • 1





        This is shell dependent, not OS dependent. I would be surprised if export ever worked like that in Bash.

        – l0b0
        Jun 17 '13 at 10:04












      • Additionally, the PATH variable is already exported and does not need to be exported again.

        – Kusalananda
        Apr 14 '18 at 9:57

















      • Basically I have created some variables, JAVA_HOME, MAVEN_HOME and want to make sure that bash has properly set them, so I export $PATH to see if the path variables have been properly set to the PATH variable

        – ThaSaleni
        Jun 17 '13 at 10:04






      • 1





        This is shell dependent, not OS dependent. I would be surprised if export ever worked like that in Bash.

        – l0b0
        Jun 17 '13 at 10:04












      • Additionally, the PATH variable is already exported and does not need to be exported again.

        – Kusalananda
        Apr 14 '18 at 9:57
















      Basically I have created some variables, JAVA_HOME, MAVEN_HOME and want to make sure that bash has properly set them, so I export $PATH to see if the path variables have been properly set to the PATH variable

      – ThaSaleni
      Jun 17 '13 at 10:04





      Basically I have created some variables, JAVA_HOME, MAVEN_HOME and want to make sure that bash has properly set them, so I export $PATH to see if the path variables have been properly set to the PATH variable

      – ThaSaleni
      Jun 17 '13 at 10:04




      1




      1





      This is shell dependent, not OS dependent. I would be surprised if export ever worked like that in Bash.

      – l0b0
      Jun 17 '13 at 10:04






      This is shell dependent, not OS dependent. I would be surprised if export ever worked like that in Bash.

      – l0b0
      Jun 17 '13 at 10:04














      Additionally, the PATH variable is already exported and does not need to be exported again.

      – Kusalananda
      Apr 14 '18 at 9:57





      Additionally, the PATH variable is already exported and does not need to be exported again.

      – Kusalananda
      Apr 14 '18 at 9:57













      16














      The following command export $PATH=somePath will return not a valid identifier and that is because of the $ before the PATH variable.



      solution:



      export PATH=somePath






      share|improve this answer



























        16














        The following command export $PATH=somePath will return not a valid identifier and that is because of the $ before the PATH variable.



        solution:



        export PATH=somePath






        share|improve this answer

























          16












          16








          16







          The following command export $PATH=somePath will return not a valid identifier and that is because of the $ before the PATH variable.



          solution:



          export PATH=somePath






          share|improve this answer













          The following command export $PATH=somePath will return not a valid identifier and that is because of the $ before the PATH variable.



          solution:



          export PATH=somePath







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 16 '15 at 19:00









          Kevin CrainKevin Crain

          26123




          26123





















              0














              You should use it this way:
              export PATH=$PATH:/something/bin
              Instead of:
              export $PATH=$PATH:/something/bin



              just remove the $ sign from the LHS





              share








              New contributor




              Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.
























                0














                You should use it this way:
                export PATH=$PATH:/something/bin
                Instead of:
                export $PATH=$PATH:/something/bin



                just remove the $ sign from the LHS





                share








                New contributor




                Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






















                  0












                  0








                  0







                  You should use it this way:
                  export PATH=$PATH:/something/bin
                  Instead of:
                  export $PATH=$PATH:/something/bin



                  just remove the $ sign from the LHS





                  share








                  New contributor




                  Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  You should use it this way:
                  export PATH=$PATH:/something/bin
                  Instead of:
                  export $PATH=$PATH:/something/bin



                  just remove the $ sign from the LHS






                  share








                  New contributor




                  Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share


                  share






                  New contributor




                  Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 3 mins ago









                  Abd ElRahman MahareekAbd ElRahman Mahareek

                  1




                  1




                  New contributor




                  Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Abd ElRahman Mahareek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





















                      -1














                      You probably had a need to append a $PATH to your existing PATH variable ?



                      export PATH=$PATH:/something/bin





                      share|improve this answer




















                      • 1





                        OK, this is in the same ball park as the question, but it’s out in left field.

                        – G-Man
                        Mar 15 '18 at 0:12















                      -1














                      You probably had a need to append a $PATH to your existing PATH variable ?



                      export PATH=$PATH:/something/bin





                      share|improve this answer




















                      • 1





                        OK, this is in the same ball park as the question, but it’s out in left field.

                        – G-Man
                        Mar 15 '18 at 0:12













                      -1












                      -1








                      -1







                      You probably had a need to append a $PATH to your existing PATH variable ?



                      export PATH=$PATH:/something/bin





                      share|improve this answer















                      You probably had a need to append a $PATH to your existing PATH variable ?



                      export PATH=$PATH:/something/bin






                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Jun 16 '18 at 13:20

























                      answered Mar 14 '18 at 23:01









                      Thad GuidryThad Guidry

                      1071




                      1071







                      • 1





                        OK, this is in the same ball park as the question, but it’s out in left field.

                        – G-Man
                        Mar 15 '18 at 0:12












                      • 1





                        OK, this is in the same ball park as the question, but it’s out in left field.

                        – G-Man
                        Mar 15 '18 at 0:12







                      1




                      1





                      OK, this is in the same ball park as the question, but it’s out in left field.

                      – G-Man
                      Mar 15 '18 at 0:12





                      OK, this is in the same ball park as the question, but it’s out in left field.

                      – G-Man
                      Mar 15 '18 at 0:12

















                      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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f79658%2fnot-a-valid-identifier-when-i-do-export-path%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

                      Frič See also Navigation menuinternal link

                      Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

                      fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox