Dear Petr
Moving CCP4 to the end of the PATH could cause some problems,
for example on Linux CCP4 truncate would be shadowed by relatively
new truncate from GNU coreutils.
We've been aware that having tclsh, wish, etc in $CCP4/bin could cause
conflicts, but since no one complained it was a
Dear Petr,
I also source the setup script $CCP4/bin/ccp4.setup-sh as I use ccp4
from the command line quite a bit. In my case (v. 6.5), the PATH is set to
PATH=$PATH:$CCP4/etc:$CCP4/bin:$CCP4/share/xia2/Applications:
i.e. CCP4 is appended, not prepended. I don't think I edited the line so
it
On Mar 13, 2015, at 12:42 PM, Petr Leiman petr.lei...@epfl.ch wrote:
this is how we are supposed to use CCP4 today anyway.
I’ve never been big on doing what I am told I am supposed to do, so I have been
using this:
use this to put it at the end of the path:
ccp4_first_in_path=0
or this
Dear All,
I have to apologize for my somewhat insinuating message about CCP4
behavior. In order to retain command line functionality of CCP4
programs, I always sourced CCP4 setup script in my bashrc file, and this
is what caused a significant amount of grief for me later. However,
sourcing
Dear Community,
What is the reason of placing the CCP4 PATH and other path-related variables in
front of existing variables? This forces a linux system to use CCP4-distributed
wish in all applications by default. Note that the ccp4i script calls CCP4
distributed wish explicitly with its full
