Force terminal to use binary from a different path

homebrewpathpythonterminal

I have installed pandoc using homebrew and the Anaconda python distribution using pyenv. I've just found that Anaconda comes with its own pandoc binary and since the pyenv shims come before homebrew in my PATH, I cannot use the homebrew (and newer) version of pandoc.

This is my current PATH

➜ ~ echo $PATH
/Users/marco/.pyenv/shims:/Users/marco/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/local/MacGPG2/bin
➜ ~ which pandoc
/Users/marco/.pyenv/shims/pandoc

Is there a way to force the terminal to use the homebrew version of a binary without breaking the PATH?

Best Answer

You can always provide the full path to the binary instead of using the PATH at all.

$ /usr/local/bin/pandoc

To make multiple executions easier, you can create an alias.

alias pandoc=/usr/local/bin/pandoc

$ which pandoc
/Users/marco/.pyenv/shims/pandoc

$ alias pandoc=/usr/local/bin/pandoc

$ which pandoc
pandoc: aliased to /usr/local/bin/pandoc

To make future executions easier, put this alias in a .profile.

To bypass the alias without removing it, prepend a \.

$ \pandoc

The ‘right way’ is still to modify your PATH.

Related Solutions

Many programs notify me that “grep/sed/uname/… not found”; some run, some don’t. My system(?) path is damaged, how to go about a diagnosing it

Your question is unclear as it seems to ask several things. However the issue re launching from the Dock can be answered.

The Dock does not call a shell. .profile and other startup scripts are only run when Terminal.app or similar starts a shell or you run a shell script via launchd etc.

To change the path used for Apps launched from the Dock, Finder or other GUI then you need to change the path your Workspace uses this is in ~/.MacOSX/environment.plist e.g. mine is

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>WAFDIR</key>
  <string>/Users/mark/src/third_party/git-svn/waf</string>

  <key>PATH</key>
  <string>/Users/mark/bin:/Users/mark/env/bin:/Users/mark/usr/local/bin:/usr/local/bin:/opt/local/bin:/usr/local/git/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/usr/libexec/binutils:</string>
</dict>
</plist>

Also have a look at this question.

Strange path environment

The issue is how you have uninstalled python. Deleting the app does remove the code but does not affect anything you have changed elsewhere will not have been undone. In this case the changes to the path have not been undone and as the installer is a simple one it keeps adding the new bit of the path to the existing path.

To fix the path you need to find the file where the PATH environment variable is altered. If you are using the bash shell (the default in recent OSX) then. . ideally it should be ~/.bashrc but probably ~/.profile or ~/.bash_profile. See other questions or manuals on what startup file bash uses) Then edit this file so that you have only one Python in it, the lines changing PATH will begin export PATH=

In general things are uninstallable if only you know exactly what they changed in install and what they write to at run time. There is no generic way to do this. The best apps have uninstallers which will do the best. You can stop the app running by deleting the .app bundle and most configuration takes up little disk space so the cost of leaving it is not high. Also most .apps do not need edits in bash files so are more self contained.

Best Answer

Related Solutions

Many programs notify me that “grep/sed/uname/… not found”; some run, some don’t. My system(?) path is damaged, how to go about a diagnosing it

Strange path environment

Related Question