Remove a path from your PATH variable

 in

If you need to remove a path from the PATH variable before your script runs add this to the beginning of the script:

  PATH=$(echo $PATH | sed -e 's;:\?/home/user/bin;;' -e 's;/home/user/bin:\?;;')

If you need, you can re-add it at the front of the list with:

  PATH=/home/user/bin:$PATH
Or you can re-add it at the end of the list with:
  PATH=$PATH:/home/user/bin

_______________________________
Related Articles
______________________

Mitch Frazier is an Associate Editor for Linux Journal.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Remove a path from your PATH variable (the tr/grep version)

Bjoern's picture

I've always been fond of the following structure:

RPATH="/home/user/bin"
PATH=$( echo ${PATH} | tr -s ":" "\n" | grep -vwE "(${RPATH})" | tr -s "\n" ":" | sed "s/:$//" )

Split path on ":", one per line. Squeeze double occurences of ":".
Remove line(s) that exactly matches path(s) to remove
Join list of paths to a new PATH. Squeeze double occurences of "\n".
Remove ":" at end of line.

If you need to remove more than one path, You just add to the RPATH variable

RPATH="/home/user/bin|/usr/games"

Why squeeze? If You have an empty path element, then current directory seems to be included. This can lead to call of unexpected programs.

shell replacement

higuita's picture

you can also try the variable replacement that bash have:

echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin

echo ${PATH/\/usr\/sbin:}
/sbin:/bin:/usr/bin

that is this works like ${variable/text-to-remove-in-this-variable}

so $PATH=${PATH/\/usr\/sbin:}

you can also do a find and replace:

echo ${PATH/\/usr\/sbin:/\/usr\/local\/sbin:}
/sbin:/bin:/usr/local/sbin:/usr/bin

the nasty part here is the need to escape the / character, but works well :)

higuita

Doesn't always work

Mitch Frazier's picture

What about the case where the path you want to remove is at the end? Including the colon in the pattern misses that case.

Mitch Frazier is an Associate Editor for Linux Journal.

Editing PATH variables.

stevenworr's picture

A much easier way to go is to let the builtin readline functions do more of the work.
Add this to your .inputrc

"\C-xp": "PATH=${PATH}\e\C-e\C-a\ef\C-f"

What it says in english is: "If I hit ^Xp, then on the commandline say PATH=$PATH. Then use escape-control-e
to cause any variables to be expanded. Then go to the beginning of the line, then go forwards by one word and then go forward by one character."

This will leave your cursor right on the first character of the value of your PATH.

After you add your sequence to the .inputrc, just say ^X^R to cause your .inputrc to be re-read.

Steven W. Orr

If you say so :)

Mitch Frazier's picture

I'll take your word for that one. Although, I was thinking more in terms of having this in a script to take out paths you don't want, and not in terms of doing it interactively at the command line.

Mitch Frazier is an Associate Editor for Linux Journal.

That doesn't always work

slu's picture

Testing the above with

PATH=/home/user/bin:/one:/home/user/bin:/two:/home/user/bin

I'm getting the following result:

:/one:/two:/home/user/bin

Instead I would suggest the following

PATH=$(echo $PATH | sed -e 's;\(^/home/user/bin:\|:/home/user/bin$\|:/home/user/bin\(:\)\);\2;g')

that gives us the following result:

/one:/two

I know my test PATH is a little extreme, as you shouldn't normally see the same path more than once in your PATH. But real life systems aren't always "normal".

Not extreme at all

Mitch Frazier's picture

Actually, that's not all that extreme of an example. Yours is better.

Mitch Frazier is an Associate Editor for Linux Journal.

White Paper
Linux Management with Red Hat Satellite: Measuring Business Impact and ROI

Linux has become a key foundation for supporting today's rapidly growing IT environments. Linux is being used to deploy business applications and databases, trading on its reputation as a low-cost operating environment. For many IT organizations, Linux is a mainstay for deploying Web servers and has evolved from handling basic file, print, and utility workloads to running mission-critical applications and databases, physically, virtually, and in the cloud. As Linux grows in importance in terms of value to the business, managing Linux environments to high standards of service quality — availability, security, and performance — becomes an essential requirement for business success.

Learn More

Sponsored by Red Hat

White Paper
Private PaaS for the Agile Enterprise

If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.

Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.

Learn More

Sponsored by ActiveState