DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=IFMTalJXS7Jj2MvsLgTba++pw9J4
	qVpM+GWk+XG8/ICfEH9apyFfO0H/OAmuGrfxl2acNGfBxZumi+h+EUJtp5KlQYe/
	o90Axf8/dkXsXy+yCfoBh/MeaetLoNNsRFsTW7WCOKLBNMq94UZ24inYhtArNwH3
	EbEz+Zrs2SmNC9U=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by CYGWIN
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <310497164.20160810040104@yandex.ru>
Date: Tue, 9 Aug 2016 19:11:13 -0600
Message-Id: <D439D5B9-BBDA-47C8-940E-7A7B19EDE02F@etr-usa.com>
References: <001001d1edf1$a4e1ae90$eea50bb0$@rogers.com> <1C0AE95E-0118-4353-AA77-4D41F1AE9AE1@solidrocksystems.com> <001a01d1eea9$f7949a90$e6bdcfb0$@rogers.com> <76ec05e9-140a-19cb-942b-698582c3d024@gmail.com> <001f01d1ef2c$f04af9e0$d0e0eda0$@rogers.com> <20160805152951.GO25811@calimero.vinschen.de> <57A6ED1C.1060402@gmx.de> <20160808112321.GF32150@calimero.vinschen.de> <e90174df-61b4-17c8-064b-30009e6ad559@gmail.com> <20160808143321.GS25811@calimero.vinschen.de> <8dc84987-802d-30d3-3ebb-2ba25871b561@gmail.com> <CACoZoo3_kBe6zWktTzydhHFzeZMr+AZe1Z2WujagTcLme_ctZg@mail.gmail.com> <310497164.20160810040104@yandex.ru>
To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On Aug 9, 2016, at 7:01 PM, Andrey Repin wrote:
> 
>> PATHEXT looks for *executable* files, not file association.  I warned
>> previously in this thread about getting the two confused.
> 
> Your statement is confusing. If not contradictory.
> PATHEXT tells the shell to consider these file extensions executable.
> If you create a file association for ".sh" and add ".SH" to pathext, CMD will
> happily execute it, and in the current console.

I think he means that if PATHEXT support appears in Cygwin (whether in the DLL or just in Bash) that you would have to chmod +x any files you want it to apply to.  The existence of the file’s extension in PATHEXT alone would not be enough.
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple