DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Pj55lu5Iog/POLWb
	f7QAHJMoQayoBQ6AcUQx6nh+7gjLt1S95iUuuAQ1AhDauS2odR8iuvhWiDsdvI8U
	f9/34SoPxLNilb0HN/+C6JZdY2hiDhtBWZAmnEK98W+XqQOT8f5HQj4jELVHB1/t
	sBEhBtGFUm6Emw9ZeLUcukdAQJI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by CYGWIN
To: cygwin@cygwin.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> <D439D5B9-BBDA-47C8-940E-7A7B19EDE02F@etr-usa.com>
From: cyg Simple <cygsimple@gmail.com>
Message-ID: <0eec2610-8ed7-ac53-18bb-041a0430894e@gmail.com>
Date: Wed, 10 Aug 2016 09:59:00 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <D439D5B9-BBDA-47C8-940E-7A7B19EDE02F@etr-usa.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 8/9/2016 9:11 PM, Warren Young wrote:
> 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.

No, adding a .sh to PATHEXT will not execute the file.
No, doing a chmod +x will not cause CMD to execute the file either even
if the extension is in the PATHEXT list.

You must associate the .sh to the executable to consume it and once you
do that association PATHEXT is meaningless.

-- 
cyg Simple

--
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