Robert Citek wrote:
On Sunday, Jan 30, 2005, at 07:08 US/Central, Tom Chapin wrote:
And I always put my current directory in my $PATH, but always at the end. (If I
am so stupid as to leave my own directories open for others to write into,
or to run unknown commands in someone else's directories, then I deserve
what I get...) Typically when I am working at some company, I always
rewrite my $PATH from scratch anyway, since the sysadmins too often give us
an /etc/profile that puts our current directory in front, and loads up
$PATH with garbage, half of which no longer exist and many of the rest I
will never use, so I hardcode what I want in my .profile.
I've seen many a flame war about whether or not it is a good idea to put "." in the PATH. My personal preference is to not, just because I'm a bit more conservative. Others, like Tom, like to put "." in the PATH. It's whatever you like, just be sure you understand the implications.
Also, I prefer to put my personal scripts in ~/bin and put ~/bin at the beginning of the PATH, like so:
export PATH=~/bin:$PATH
My reasoning is that, if I've created a script with the same name as an existing program, then it's probably because I want behaviour that differs from the existing program.
In the end, it's all just personal preference. And unix/linux/BSD allows you to customize your work environment to suit your personal preferences.
Regards, - Robert
Thanks for the great advice guys. This discussion is very informative and confirms what I was a bit unsure about. I will create a directory for learning and use $HOME/bin as designed.
Their could not be a better group for scripting questions!
-- Jerry Hubbard [EMAIL PROTECTED]
_______________________________________________
CWE-LUG mailing list
http://www.cwelug.org/ [email protected]
http://lists.firepipe.net/listinfo/cwe-lug
