> -----Original Message----- > From: Beni Cherniavsky > Sent: Sunday, February 23, 2003 2:54 PM > Cc: [EMAIL PROTECTED] > Subject: RE: Problem with Pth or make or what? > > Good advice. Indeed a quick grep of scripts in /usr/bin > shows most reset > the path. I was refering to my own ~/bin scripts and shell > aliases where > I'm too lazy to do it. Perhaps I'm wrong but PATH is > intended to avoid > typing the full pathes, not to bring the need back.
You are right - but once you set the $PATH you can relay on it and use "relative" program names. Or what many (more "robust") scripts do is to lookup the individual programs and set a script variable for each one of them (e.g. "$AWK = lookup(awk)" then use $AWK everywhere in the script). As for laziness - it might cause you a headache one day when your environment changes or you want to copy it over to somewhere else, better maintain it now. > On a second thought, having '.' in the *end* of the path is > almost safe. I'd say it's pretty safe, but I still wouldn't put it in the root path. > Not that I'd use it anyway, I'm typing dotslash automatically now :-). Me too :). I just noticed that I don't have '.' in my path, I was sure I have it as I always had. Damn habits.... --Amos ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
