[EMAIL PROTECTED] wrote:
> I see, so even though pth1_ seems to be a list of
> separate directories, it doesn't fully work like that, therefore
> if an application asks for where to look for it's data, you can't just
> use pth1_
> expecting the application to see all the data even if you've setup
> pth1_ to point to all the places where that data should exist.
>
> Shame that !
Morning Neil,
on Linux/Unix (and similarly in Win/DOS too) you do something like this :
export PATH=folder_1:folder_2:folder_3:folder_etc
That sets the PATH variable to hold a list of directories that you wish to use
so that the system will find a program to execute when you say something like @
myProg param_1 param_2 Param_etc
If the executable for 'myProg' is on one of the directories held in the PATH
variable, then the OS will find it and execute it.
You can, in *nix do this :
ls $PATH
(The '$' de-references the variable and uses the contents) but that doesn't
give you a directory listing of each directory in the PATH variable, it simply
lists the various directories (well, it does here !).
The PATH variable isnt used when opening a file, if I try to edit a file that
is in a directory on my PATH, then it fails to open because it is not in the
current directory (that I have cd'd to).
The PTH driver is similar to PATH on *nix. Use it for finding and execution
binaries, not for opening files, directory listings or saving datat files.
HTH
Cheers,
Norman.
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
