From:	vos AT channelpoint DOT com (Craig Vosburgh)
Subject:	RE: cygwin b20 bash path usage?
11 Nov 1998 16:01:58 -0800 :
Message-ID:	<8A24EC12044FD21195E200600895E0B3059484.cygnus.gnu-win32@goat.channelpoint.com>
Mime-Version:	1.0
To:	"'William D Kirby'" <wdkirby AT ix DOT netcom DOT com>,
	"'gnu-win32 AT cygnus DOT com'"
	<gnu-win32 AT cygnus DOT com>

bash will use the PATH variable to determine the search order.  It
sounds like you need to put . in your PATH variable first or execute the
test command as ./test.  If you have any question which executable is
being executed you can always use the type command to see what bash hash
hashed for that name (e.g. type test should return the path to the test
executable being executed)

-Craig

> -----Original Message-----
> From: owner-gnu-win32 AT cygnus DOT com [mailto:owner-gnu-win32 AT cygnus DOT com]On
> Behalf Of William D Kirby
> Sent: Monday, November 09, 1998 7:44 PM
> To: gnu-win32 AT cygnus DOT com
> Subject: cygwin b20 bash path usage? 
> 
> 
> I made the mistake of creating and trying to use an exectable named
> test.exe. under bash v2.02 in the cygwin beta 20 package. Nothing
> happened when it executed. I suspect that bash was executing 
> the program
> test.exe in the cygwin-b20\bin directory rather my test.exe in the
> directory I was using.
> 
> Is this proper behavior in bash? I assumed the directory 
> being worked in
> was searched first then along the PATH directory list.
> 
> Bill
> 
> --
> William D. Kirby             Voice: (703) 273-0005
> Consultant                   Email: wdkirby AT ix DOT netcom DOT com
> 3527 Cornell Road
> Fairfax, VA 22030-1813
> 
> 
> 
> 
> -
> For help on using this list (especially unsubscribing), send 
> a message to
> "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
> 
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -