Mac OSX doesn't guarantee praat in PATH

[chrisbrickhouse]

Troubleshooting use of fave/extractFormants.py on a fresh install of Fave2.0.0 and we ran into the problem of praat not being in PATH. The program was installed, but it seems to live in the Applications directory which is not normally in PATH. This means that the search on line 2090 fails, and the user (who has praat installed) is left with a confusing message about how the program cannot be found.

The workaround we found was to edit the user's ~/.bash_profile so that the applications directory is added to their PATH when starting their terminal session. I'd argue this is not ideal. Adding the whole applications folder to their PATH introduces a vulnerability, and adding the specific Praat folder to their PATH is fragile should praat ever change its directory structure or install location. It's probably also not the best idea to encourage end users to play around in their bash profile. This all goes double for asking them to symlink to praat from their /usr/local/bin

The best solution, I think, is a more intelligent search for praat. If the search fails (line 2097) it would make sense to search for an ~/Applications directory and see if we can find a praat executable in there (probably with a warning in case it's old or broken). If so, use it, and if not fail with some additional information. Thoughts?