Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 30 Aug 2004 11:47:36 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Running Windows scripts & PATHEXT
Message-ID: <20040830154736.GP8900@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <cgvhro$5uj$1 AT sea DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cgvhro$5uj$1@sea.gmane.org>
User-Agent: Mutt/1.4.1i

On Mon, Aug 30, 2004 at 08:41:38AM -0700, Andrew DeFaria wrote:
>So it seems that bash does not take into account the PATHEXT variable
>when searching for executables.  Now I know that PATHEXT is very
>Window'ish and bash need not support it but perhaps Cygwin's bash does
>somehow and I merely need to configure it correctly?

I would surely hope that bash would not be bloated to support a
windows-ism like this.

However, it seems like simply downloading the bash sources and searching
for the string "PATHEXT" would satisfy our curiousity.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/