William Scott wrote:
..
So I think your process is getting killed before you look at the cat in
the box. If it is a question of ${CCP4I_TCLTK} not getting assigned, the
error you should see looks like this:
bash: /bltwish: No such file or directory
bash: exec: /bltwish: cannot execute: No such file or directory
It seems bash treats undefined variables as the null string:
bash-3.2$ echo ${wxyz}/abc
/abc
while csh prints an error message, but not like the OP's:
oswego 185% echo ${wxyz}/abc
wxyz: Undefined variable.
apparently tcl gives the error message reported:
oswego 187% tclsh
% printf ${wxyz}/abc
can't read "wxyz": no such variable
So I think the "exec" is successful but some ensuing tcl script is
not inheriting the environment.
