Perhaps the confusion here is that Windows looks in the logged directory
FIRST and executes "namedcommand" if found. If the "namedcommand" is not
found it then searches the path, in order, and executes the first match it
finds. I found this handy and will alter my bash preferences to search the
local directory first, as suggested by Jim and others. Thanks, didn't know
this behavior was that easy to alter.
-Gary-
In a message dated 6/2/2000 3:27:59 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
<<
> Can someone please explain the concept behind ./ in executing a command.
>
The . tells the system to look in the current directory, it is needed when
you
are trying to execute a program or shell script and your working directory
is
NOT in you path. The PATH environment variable tells the system where to
look
for programs and files on your system.
Joseph H. Perry
Oracle DBA
Columbus State University
4225 University Ave
Columbus, GA 31907-5645
(706) 568-2063
[EMAIL PROTECTED]
>>
