Re: [ferret_users] Partially resolved, pyferret on osx 10.11.5

Hi Denise,

Where are you getting the ferret and pyferret source for the builds? I ask as there are now a couple of options. There are, of course, the source tar files from ferret.pmel.noaa.gov (so v6.96; v7.0 to be released in the next day or two), but now there are also GitHub repositories which are regularly updated with the latest:
https://github.com/NOAA-PMEL/Ferret.git
https://github.com/NOAA-PMEL/PyFerret.git
Thanks to Filipe in Brazil, there is an Anaconda build of PyFerret (for Linux and Mac under python 2.7) that we are testing.
(If you wish help test, please let me know.)

Although Ferret and PyFerret can co-exist under the same directory, it is simpler to keep them in separate directories. The duplicated scripts and environment files do not amount to much disk space. Keeping them in separate directories allows you to just source the default generated ferret_paths scripts for whichever program you want to use and then run that program. Since the pyferret program is actually a shell script, some users add the "source"-ing (actually the "." command for sh) of the ferret_paths.sh script to the pyferret script. A "ferret" script could be created which "source" the ferret_paths.sh for ferret and then runs the ferret_v... executable.

Not sure what might be turning off the echo-ing of command-line input. Might try "stty echo" to see if that restores the echo-ing (or "stty sane" to return to a sane configuration). But this is the first I have heard of this happening. Please do follow up with me off-list on this.

Best regards,

Karl

On Sun, Jul 10, 2016 at 6:13 AM, Denise Worthen - NOAA Affiliate <denise.worthen@xxxxxxxx> wrote:

My apologies for cluttering up the list...

I've resolved the error which I had posted about. One of two things I did resolved it.

One, I had missed a INSTALL_FER_DIR setting in the external_functions/ef_utility/site_specific.mk. Secondly, I re-compiled w/ PYTHON_EXE set explicitly to my macports python2.7 install. I suspect it was the first thing that fixed it.

At this point, I can sort of get pyferret to work, but only in tcsh. In bash, entering and exiting pyferret seems to corrupt the shell. Commands become invisible, ie, "ls" produces output but the command "ls" does not echo to the screen.

I'm also confused about how to have both ferret and pyferret peacefully coexisting (ferret_paths etc.)

Any help (off-list perhaps) would be appreciated!

Thanks,
Denise

Karl M. Smith, Ph.D.
JISAO Univ. Wash. and PMEL NOAA
"The contents of this message are mine personally and do
not necessarily reflect any position of the Government
or the National Oceanic and Atmospheric Administration."