I'm wondering where a new path has to be added to the PATH environment variable. I know this can be accomplished by editing .bashrc (for example), but it's not clear how to do this.

This way:

export PATH=~/opt/bin:$PATH

or this?

export PATH=$PATH:~/opt/bin
  • printf '\nPATH=$PATH:"path-to-add"\nexport PATH\n' >> ~/.bashrc – Persian Nov 7 '14 at 13:04
  • 2
  • If there are already some paths added, e.g. PATH=$PATH:$HOME/.local/bin:$HOME/bin, another can be added by separating with a : e.g. PATH=$PATH:$HOME/.local/bin:$HOME/bin:/home/ec2-user/pear/bin. – Sandeepan Nath Aug 20 '16 at 18:40
  • Do these answers work for all flavors of linux? – Ungeheuer Nov 20 '16 at 20:58

11 Answers 11

up vote 811 down vote accepted

The simple stuff


depending on whether you want to add ~/opt/bin at the end (to be searched after all other directories, in case there is a program by the same name in multiple directories) or at the beginning (to be searched before all other directories).

You can add multiple entries at the same time. PATH=$PATH:~/opt/bin:~/opt/node/bin or variations on the ordering work just fine.

You don't need export if the variable is already in the environment: any change of the value of the variable is reflected in the environment.¹ PATH is pretty much always in the environment; all unix systems set it very early on (usually in the very first process, in fact).

If your PATH gets built by many different components, you might end up with duplicate entries. See How to add home directory path to be discovered by Unix which command? and Remove duplicate $PATH entries with awk command to avoid adding duplicates or remove them.

Where to put it

Note that ~/.bash_rc is not read by any program, and ~/.bashrc is the configuration file of interactive instances of bash. You should not define environment variables in ~/.bashrc. The right place to define environment variables such as PATH is ~/.profile (or ~/.bash_profile if you don't care about shells other than bash). See What's the difference between them and which one should I use?

Notes on shells other than bash

In bash, ksh and zsh, export is special syntax, and both PATH=~/opt/bin:$PATH and export PATH=~/opt/bin:$PATH do the right thing even. In other Bourne/POSIX-style shells such as dash (which is /bin/sh on many systems), export is parsed as an ordinary command, which implies two differences:

So in shells like dash, export PATH=~/opt/bin:$PATH sets PATH to the literal string ~/opt/bin/: followed by the value of PATH up to the first space. PATH=~/opt/bin:$PATH (a bare assignment) doesn't require quotes and does the right thing. If you want to use export in a portable script, you need to write export PATH="$HOME/opt/bin:$PATH", or PATH=~/opt/bin:$PATH export PATH (or PATH=$HOME/opt/bin:$PATH export PATH for portability to even the Bourne shell that didn't accept export var=value and didn't do tilde expansion).

¹ This wasn't true in Bourne shells (as in the actual Bourne shell, not modern POSIX-style shells), but you're highly unlikely to encounter such old shells these days.

  • 13
    Something to add is that if PATH is empty (unlikely, but it could happen), then PATH=some/path:$PATH will add the current directory to the PATH, which could potentially be exploited by an attacker. – James Tocknell Mar 17 '15 at 11:55
  • 1
    @Tim In an assignment, the quotes are optional. (They are necessary in some shells with export VAR=…, but never with a plain VAR=….) See unix.stackexchange.com/questions/68694/… for the gory details. You might want to always use quotes just to avoid remembering when they're necessary and when they aren't. – Gilles Apr 6 '15 at 21:48
  • 2
    @Naveen I have no idea what you're asking. Will what work and what “file system folder” are you talking about? Normally you can't edit files in /etc unless you're the administrator, but you can edit files in your home directory. – Gilles Aug 26 '15 at 18:50
  • 1
    @Startec A mistake, possibly due to joining two lines in a bad way. It doesn't hurt anything except performance in the case when an executable is not found. – Gilles Sep 25 '15 at 8:05
  • 1
    @kapad One way to tell is that a variable is in the environment if it's listed by export with no parameters. Once a variable is in the environment (because it's been exported at least once), it stays there until it's unset. If you change the value of the variable, that changes its value in the environment. Since the login process sets PATH in the environment, you'd have to do something unusual to get an environment without PATH, for example using env -u or env -i. – Gilles Feb 12 at 22:05

Either way works, but they don't do the same thing: the elements of PATHare checked left to right. In your first example, executables in ~/opt/bin will have precedence over those installed, for example, in /usr/bin, which may or may not be what you want.

In particular, from a safety point of view, it is dangerous to add paths to the front, because if someone can gain write access to your ~/opt/bin, they can put, for example, a different ls in there, which you'd then probably use instead of /bin/ls without noticing. Now imagine the same for ssh or your browser or choice... (The same goes triply for putting . in your path.)

  • 4
    But if you want to have your own, customized version of ls, you need to put it in a directory ahead of /bin. – Barmar Sep 17 '15 at 20:20
  • 11
    or alias ls=myls – waltinator Sep 18 '15 at 1:27

I'm confused by question 2 (since removed from the question since it was due to an unrelated issue):

What's a workable way to append more paths on different lines? Initially I thought this could do the trick:

export PATH=$PATH:~/opt/bin
export PATH=$PATH:~/opt/node/bin

but it doesn't because the second assignment doesn't only append ~/opt/node/bin, but also the whole PATH previously assigned.

This is a possible workaround:

export PATH=$PATH:~/opt/bin:~/opt/node/bin

but for readability I'd prefer to have one assignment for one path.

If you say


that's all that will be in your PATH. PATH is just an environment variable, and if you want to add to the PATH, you have to rebuild the variable with exactly the contents you want. That is, what you give as an example to question 2 is exactly what you want to do, unless I'm totally missing the point of the question.

I use both forms in my code. I have a generic profile that I install on every machine I work on that looks like this, to accommodate for potentially-missing directories:

export PATH=/opt/bin:/usr/local/bin:/usr/contrib/bin:/bin:/usr/bin:/usr/sbin:/usr/bin/X11
# add optional items to the path
for bindir in $HOME/local/bin $HOME/bin; do
    if [ -d $bindir ]; then
  • 2
    You are right about the example of question 2, it works. Another PATH related issue on my system confused me. Sorry for that. – Paolo Dec 5 '11 at 0:59

Linux determines the executable search path with the $PATH environment variable. To add directory /data/myscripts to the beginning of the $PATH environment variable, use the following:


To add that directory to the end of the path, use the following command:


But the preceding are not sufficient because when you set an environment variable inside a script, that change is effective only within the script. There are only two ways around this limitation:

  • If, within the script, you export the environment variable it is effective within any programs called by the script. Note that it is not effective within the program that called the script.
  • If the program that calls the script does so by inclusion instead of calling, any environment changes in the script are effective within the calling program. Such inclusion can be done with the dot command or the source command.


source $HOME/myscript.sh

Inclusion basically incorporates the "called" script in the "calling" script. It's like a #include in C. So it's effective inside the "calling" script or program. But of course, it's not effective in any programs or scripts called by the calling program. To make it effective all the way down the call chain, you must follow the setting of the environment variable with an export command.

As an example, the bash shell program incorporates the contents of file .bash_profile by inclusion. So putting the following 2 lines in .bash_profile:

export PATH

effectively puts those 2 lines of code in the bash program. So within bash the $PATH variable includes $HOME/myscript.sh, and because of the export statement, any programs called by bash have the altered $PATH variable. And because any programs you run from a bash prompt are called by bash, the new path is in force for anything you run from the bash prompt.

The bottom line is that to add a new directory to the path, you must append or prepend the directory to the $PATH environment variable within a script included in the shell, and you must export the $PATH environment variable.

More information here

For some time now I've kept with me two functions pathadd and pathrm that assist in adding elements to the path without the need to worry about duplications.

pathadd takes a single path argument and an optional after argument which if supplied will append to the PATH otherwise it prepends it.

In almost every situation if you're adding to the path then you're likely wanting to override anything already in the path, which is why I opt to prepend by default.

pathadd() {
    if [ -d "$1" ] && ! echo $PATH | grep -E -q "(^|:)$newelement($|:)" ; then
        if [ "$2" = "after" ] ; then

pathrm() {
    PATH="$(echo $PATH | sed -e "s;\(^\|:\)${1%/}\(:\|\$\);\1\2;g" -e 's;^:\|:$;;g' -e 's;::;:;g')"

Put these in any script you wish to alter the PATH environment and you can now do.

pathadd "/foo/bar"
pathadd "/baz/bat" after
export PATH

You're guaranteed not to add to the path if it's already there. If you now want to ensure /baz/bat is at the start.

pathrm "/baz/bat"
pathadd "/baz/bat"
export PATH

Now any path can be moved to the front if it's already in the path without doubling.

The bullet-proof way of Appending/Prepending

There are a lot of considerations involved in the choice of appending versus prepending. Many of them are covered in other answers, so I will not repeat them here.

An important point is that, even if system scripts do not use this (I wonder why)*1, the bullet-proof way to add a path (e.g., $HOME/bin) to the PATH environment variable is


for appending (instead of PATH="$PATH:$HOME/bin") and


for prepending (instead of PATH="$HOME/bin:$PATH")

This avoids the spurious leading/trailing colon when $PATH is initially empty, which can have undesired side effects and can become a nightmare, elusive to find (this answer briefly deals with the case the awk-way).

Explanation (from Shell Parameter Expansion):


If parameter is null or unset, nothing is substituted, otherwise the expansion of word is substituted.

Thus, ${PATH:+${PATH}:} is expanded to: 1) nothing, if PATH is null or unset, 2) ${PATH}:, if PATH is set.

Note: This is for bash.

*1 I have just found that scripts like devtoolset-6/enable actually use this,

$ cat /opt/rh/devtoolset-6/enable
# General environment variables
export PATH=/opt/rh/devtoolset-6/root/usr/bin${PATH:+:${PATH}}

I can't speak for other distributions, but Ubuntu has a file, /etc/environment, that is the default search path for all users. Since my computer is only used by me, I put any directories that I want in my path there, unless it is a temporary addition that I put in a script.

Here is my solution:

PATH=$(echo -n $PATH | awk -v RS=: -v ORS=: '!x[$0]++' | sed "s/\(.*\).\{1\}/\1/")

A nice easy one liner that doesn't leave a trailing :

  • -bash: awk: No such file or directory -bash: sed: No such file or directory – davidcondrey Nov 21 '16 at 19:18
  • 1
    @davidcondrey - awk and sed are very common external commands. This answer provides a pure-bash way of achieving the same, so it works even in cases when awk and/or sed are not present (or their respective directories are not in the path!) – sancho.s Jan 19 at 9:45

For me (on Mac OS X 10.9.5), adding the path name (e.g. /mypathname) to the file /etc/paths worked very well.

Before editing, echo $PATH returns:


After editing /etc/paths and restarting the shell, the $PATH variable is appended with /pathname. Indeed, echo $PATH returns:


What happened is that /mypathname has been appended to the $PATH variable.

  • 2
    Better to add a file to the /etc/paths.d directory than to edit the /etc/paths file itself. – rbrewer Sep 7 '16 at 20:50

To add a new path to the PATH environment variable:

export PATH=$PATH:/new-path/

For this change to be applied to every shell you open, add it to the file that the shell will source when it is invoked. In different shells this can be:

  • Bash Shell: ~/.bash_profile, ~/.bashrc or profile
  • Korn Shell: ~/.kshrc or .profile
  • Z Shell: ~/.zshrc or .zprofile


# export PATH=$PATH:/root/learning/bin/
# source ~/.bashrc
# echo $PATH

You can see the provided path in the above output.

There are some situations where it using PATH=/a/b:$PATH might be considered the "incorrect" way to add a path to PATH:

  1. Adding a path that's not actually a directory.
  2. Adding a path that's already in PATH in the same form.
  3. Adding a relative path (since the actual directory searched would change as you change the current working directory).
  4. Adding a path that's already in PATH in a different form (i.e., an alias due to using symlinks or ..).
  5. If you avoid doing 4, not moving the path to the front of PATH when it's intended to override other entries in PATH.

This (Bash-only) function does the "right thing" in the above situations (with an exception, see below), returns error codes, and prints nice messages for humans. The error codes and messages can be disabled when they're not wanted.

prepath() {
    local usage="\
Usage: prepath [-f] [-n] [-q] DIR
  -f Force dir to front of path even if already in path
  -n Nonexistent dirs do not return error status
  -q Quiet mode"

    local tofront=false errcode=1 qecho=echo
    while true; do case "$1" in
        -f)     tofront=true;       shift;;
        -n)     errcode=0;          shift;;
        -q)     qecho=':';          shift;;
        *)      break;;
    esac; done
    # Bad params always produce message and error code
    [[ -z $1 ]] && { echo 1>&2 "$usage"; return 1; }

    [[ -d $1 ]] || { $qecho 1>&2 "$1 is not a directory."; return $errcode; }
    dir="$(command cd "$1"; pwd -P)"
    if [[ :$PATH: =~ :$dir: ]]; then
        $tofront || { $qecho 1>&2 "$dir already in path."; return 0; }
        PATH="${PATH#$dir:}"        # remove if at start
        PATH="${PATH%:$dir}"        # remove if at end
        PATH="${PATH//:$dir:/:}"    # remove if in middle

The exception is that this function does not canonicalize paths added to PATH via other means, so if a non-canonical alias for a path is in PATH, this will add a duplicate. Trying to canonicalize paths already in PATH is a dicey proposition since a relative path has an obvious meaning when passed to prepath but when already in the path you don't know what the current working directory was when it was added.

protected by heemayl May 10 '17 at 13:33

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.