> Oops. I'll get rid of that "feature". However, I'm having trouble
> doingthe equivalent in Python - I tried this:
>
> run_scheme_command("define *probe-command* \"%s\"" % probe_command)
>
> and it gave me this output:
>
> INFO:: Command: define *probe-command*
> "/Users/nat/phenix/src/build
On Mon, Aug 17, 2009 at 9:50 AM, Ben Eisenbraun wrote:
> > The Phenix GUI will modify this file (only if you launch Coot from it) to
> > ensure that Coot can find Probe, which could be causing the problem - I
> > didn't take into account the possibility of a home directory being shared
> > across
Hi Nat,
> > Is Coot doing some magic when it tries to figure out where probe/reduce are
> > installed? Grepping through the source looking for phenix didn't turn
> > anything obvious up.
>
> The file ~/.coot may define a specific binary, which I assume will override
> anything in $PATH.
That wa
On Mon, Aug 17, 2009 at 8:32 AM, Ben Eisenbraun wrote:
> I have a very odd issue. I have two builds of Coot, one for OS X Intel and
> one for OS X PPC. On each of those platforms, I have a standalone
> probe/reduce in the shell PATH. When I run either of these Coots, they
> manage to find and t
I have a very odd issue. I have two builds of Coot, one for OS X Intel and
one for OS X PPC. On each of those platforms, I have a standalone
probe/reduce in the shell PATH. When I run either of these Coots, they
manage to find and try to use the phenix.probe installed in our linux
branch.
>Fro
