Add to $PATH with Shell Script [duplicate]

Question

I want to add PATH on Linux Ubuntu 18.04 from file path.sh , my file include :

 #!/bin/bash
 export PATH="$PATH:/root/.local/bin"

chmod+x path.sh , but when i run it ./path.sh Path not add when i type echo $PATH .

but when i type in terminal export PATH="$PATH:/root/.local/bin" it added to my PATH .

Am I miss something on my file?

Can't add an answer to this anymore, but a less common solution to this problem—particularly if source doesn't fit your needs—is to leverage exported functions and/or aliases to update your PATH. function myPath() { export PATH="/whatever/bin:$PATH" } export -f myPath Then, add this to your .bashrc or equivalent: source ~/myPath.sh (apologies in advance for crappy comment formatting restrictions) — LyrePyre
– LyrePyre, Commented May 3, 2024 at 23:20
^ Really handy alternative if, for example, you have a bin directory on an external drive or perhaps a partition that isn't always mounted, mounted at different paths on different machines, etc. Personally I put my mount/umount shortcuts into exported functions like these to handle both mounting and updating the environment (PATH etc) in one swoop. — LyrePyre
– LyrePyre, Commented May 3, 2024 at 23:27

bbotte · Accepted Answer · 2018-12-11 08:20:55Z

2

source path.sh

add this step is fine.

answered Dec 11, 2018 at 8:20

bbotte

1905 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Micha Wiedenmann · Accepted Answer · 2018-12-11 08:12:42Z

1

Let's consult man bash:

export [-fn] [name[=word]] ...
export -p
       The  supplied names are marked for automatic export to the envi-
       ronment of subsequently executed commands.

Note "subsequently executed commands", therefore the effect of your script ends, once the script ends.

answered Dec 11, 2018 at 8:12

Micha Wiedenmann

21.1k22 gold badges96 silver badges142 bronze badges

1 Comment

LyrePyre Over a year ago

I don't think this really answers OP, or at least not very clearly. In the absence of your additional commentary, the quoted man entry seems to already describe OP's working understanding of export—it adds noise, without offering new insight. More direct insight sans manpage: (1) Running a script (./) creates a child shell of the calling shell, and inherits a copy of its environment; and (2) export can only propagate forwards in this inheritance tree, and cannot copy variables "backwards" to the calling environment after exiting. This is why running doesn't work, but source does.

Collectives™ on Stack Overflow

Add to $PATH with Shell Script [duplicate]

2 Answers 2

Comments

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Linked

Related