When you type in a program to be executed, bash will search for the
programs based on what's in your PATH environmental variable.
If you don't have "./" in your PATH, it won't look there
for the program. Just add "./" to your PATH in .bash_profile, it will fix
the problem. It's a matter of taste whether you want it to look in
the current dir or not I guess.
Someting like:
vi .bash_profile
/PATH
PATH=$PATH:$HOME/bin:./
Barry Winch wrote:
> Can someone please explain the concept behind ./ in executing a command.
>
> If I am in the directory where the programme resides and type the programme
> name, I get a:
> "bash: programme name: command not found" message
>
> If, from the same directory I type ./programme name everything works as
> advertised.
>
> Thanks
>
> Barry
--
CF 10K Walk: http://members.home.net/jimgbrown/strides.html
____ ___
\/\_\@ ____ / /\ __ ___ ___ [EMAIL PROTECTED]
/ / /\ / / /\ /--/ //\_\/\_/\ /\/\/\ /\_/\ [EMAIL PROTECTED]
/__/ / / // / / / /__/ // / /__/ //_/_/ // // / home: (972)495-3821
\__\/ \/ \/\/\/ \__\/ \/ \__\/ \_\_\/ \/ \/ work: (972)889-4228
Cole's Law: Thinly sliced cabbage.
