Take the 2-minute tour ×
export PATH=/usr/local/bin:/Users/rodrigoprugue/Desktop/CRUNCH:~/phreeqc/bin:$PATH
export PARFLOW_DIR=~/parflow/parflow.r605/
export SILO_DIR=~/parflow/silo-4.7.2/
export HYPRE_DIR=~/parflow/hypre-2.4.0b/
export CC=gcc
export CXX=g++
export FC=gfortran
export F77=gfortran

Can someone tell me why my path for phreeqc will not work?

share|improve this question
Where did you put them; what's your distribution –  warl0ck Apr 14 '13 at 6:06
What does echo $PATH return? Is that configuration file even run for new shells? Try adding something like echo a to it. You can run bash -v (or -lv for login shells or OS X) to see if $PATH gets overridden later. –  ؘؘؘؘ Apr 14 '13 at 11:01
You're not giving nearly enough info for us to help you troubleshoot. Which conf file are these exports coming from? What makes you say the path "will not work"? What's the error message you're getting? Can you do an echo $PATH in the exact same shell where you'd get an error? –  rahmu Apr 15 '13 at 9:55

1 Answer 1

From the bash manual Edition 4.2, last updated 28 December 2010, of The GNU Bash Reference Manual, for Bash, Version 4.2.

3.5.2 Tilde Expansion

If a word begins with an unquoted tilde character (‘~’), all of the characters up to the first unquoted slash (or all characters, if there is no unquoted slash) are considered a tilde-prefix (...) Each variable assignment is checked for unquoted tilde-prefixes immediately following a ‘:’ or the first ‘=’. (...)

So it should work. Maybe it does not work for other versions.

share|improve this answer

Your Answer


