I find that if you give the full path to the programs and files it always works, otherwise you might have problems.
Yes but after a while to type the whole path is annoying and aslo easily introduce type errors. One way to avoid it is to use global or local variables. For example I use:
export pp=~/chess/polyglot
in my .profile. Changing glaurung's ini looks like "vim $pp/glaurung.ini" in stead of "vim /home/volker/chess/polyglot/glaurung.ini" for example.
What is best for one's system depends highly what he wants to do.
Volker Pittlik wrote:
Yes but after a while to type the whole path is annoying and aslo easily introduce type errors. One way to avoid it is to use global or local variables.
Variables in ~/.profile or other places are not always read by Scid. This includes the $PATH variable.
If I start scid from a terminal, which has all the variables set, then polyglot works even if I give "polyglot" as the command in the engine configuration window (because it is in my $PATH).
But if I start it from the menu, it does not find polyglot this way. I have to give the full path.
So in this case, which is the most usual, I don't think you can avoid giving the full path. This is what I meant when I wrote that sometimes you might have problems if you don't.