daemon@houligan.UUCP (12/21/85)
In article <6224@utzoo.UUCP>, henry@utzoo.UUCP (Henry Spencer) writes: >> As a compromise, how about setting PATH at the beginning of the script? > > This is not a compromise, it is the correct and complete solution. Don't > forget to do "export PATH". I think that it would depend on the application. It is possible that the user has directories in his PATH which would not be found by "sub- commands" if you "export" the PATH. In general, I set the PATH, but do not "export" it, and this seems to work well. Especially if one of the effects of the script is to call up another shell (rarely) or the editor (more common). Then, the user can still use all the commands he's used to. Sorry if the topic wasn't clear here. I was only discussing the point of "export"ing PATH. I agree that setting PATH is the best solution. --tgi while (--tgi) /* my mind continues to decay */ ; /* even though I do nothing.. */ {brl-bmd,ccvaxa,pur-ee,sun}!csd-gould!midas!tgi (Craig Strickland @ Gould) 305/587-2900 x5014 CompuServe: 76545,1007 Source: BDQ615 MCIMail: 272-3350 (echo ".ft B"; echo ".ps 999"; echo "$disclaimer") | troff -t # :-)