Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <002f01bff8cf$40d3e310$3c5350d8@guinness>
From: "Matthew Smith" <matts@bluesguitar.org>
To: "Noel L Yap" <yap_noel@jpmorgan.com>
Cc: <Cygwin@Sourceware.Cygnus.Com>
References: <8525692A.006CFD07.00@nyc-ntgw-n01.ny.jpmorgan.com>
Subject: Re: sh problem
Date: Fri, 28 Jul 2000 15:06:01 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

It says something along the lines of ". is not a recognized command".  At
the moment, I deal with the problem by putting "." in my path, but that
doesn't seem like a very good solution.


> In what way does it fail?
>
> Noel
>
>
>
>
> matts@bluesguitar.org on 2000.07.28 15:35:14
>
> To:   cygwin@sourceware.cygnus.com
> cc:   (bcc: Noel L Yap)
> Subject:  sh problem
>
>
>
>
> I'm having some problems with sh under windows 2k.  It seems if I try
> writing a script that references ".", as in:
>
> #!/bin/sh
>
> # access some other shell script
> ./myscript.sh
>
>
> This will fail under windows 2k, but works fine under NT 4.  Is this a
known
> problem?
>
> cheers,
> -Matt Smith
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
>
>
>
>
> This communication is for informational purposes only.  It is not intended
as
> an offer or solicitation for the purchase or sale of any financial
instrument
> or as an official confirmation of any transaction. All market prices, data
> and other information are not warranted as to completeness or accuracy and
> are subject to change without notice. Any comments or statements made
herein
> do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
> subsidiaries and affiliates.
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com