Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199904092043.PAA20484@casbah.acns.nwu.edu>
X-Sender:	dye053 AT casbah DOT acns DOT nwu DOT edu
X-Mailer:	QUALCOMM Windows Eudora Pro Version 4.0.1
Date:	Fri, 09 Apr 1999 15:42:44 -0500
To:	cygwin AT sourceware DOT cygnus DOT com
From:	mitia AT nwu DOT edu
Subject:	Re: B20.1: Scripts not executed in the current directory (bash)
In-Reply-To:	<19990409161150.A1306@cygnus.com>
References:	<370E527E DOT F4B3052F AT nwu DOT edu>
	<370E527E DOT F4B3052F AT nwu DOT edu>
Mime-Version:	1.0

Thanks all for replies.  I did as was suggested: added the current
directory to the PATH env. variable, and it solved the problem:

In .bashrc:

PATH=./:$PATH

>On Fri, Apr 09, 1999 at 02:18:22PM -0500, dye053 wrote:
>>In B20.1 I noticed a problem that I didn't have with B20 release:
>>
>>In bash, scripts with shebang (#!) are not excuted in the current
>>directory, although they are correctly identified as executable files by
>>ls.  On the other hand, scripts located in a different directory are
>>executed without a problem.
>>
>>A workaround is to call the interpreter explicitly, e.g. perl foo.pl
>>
>>Anyone else have this problem?


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -