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=v2p8Jvyeit3C4Lh+
	HAP2rtw2hIeX47lk9nTBN4cqVVDfXyJzqhlu3pxKMmmbBWOh7ht8Hb3AaDUvCuG7
	zw0NXWMt46bCE067iGG/Rg6RuSMyycaL/2V7Kw5kryv6J58rZzO9gNuFSELyoVFY
	W8jcB5pdN4oOJi5BarHF20D6PNg=
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
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by CYGWIN
To: cygwin AT cygwin DOT com
References: <001001d1edf1$a4e1ae90$eea50bb0$@rogers.com> <1C0AE95E-0118-4353-AA77-4D41F1AE9AE1 AT solidrocksystems DOT com> <001a01d1eea9$f7949a90$e6bdcfb0$@rogers.com>
From: cyg Simple <cygsimple AT gmail DOT com>
Message-ID: <76ec05e9-140a-19cb-942b-698582c3d024@gmail.com>
Date: Fri, 5 Aug 2016 10:12:14 -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: <001a01d1eea9$f7949a90$e6bdcfb0$@rogers.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Michael,

You need to configure your email client to wrap your text at no more
than 78 characters, 72 would be even better.  It helps quoting what you
write better.

You also need to stop top posting or remove the trailing mail from the
reply if quoting that particular mail isn't necessary.

Cygwin Community,

This conversation has driven me bonkers.  Cygwin is a tool for windows
first and foremost.  It was designed to help make life for those who
support both UNIX and Windows servers a little easier by not having to
convert scripts and utilities.  Cygwin is now trying to be something
more by becoming even more UNIX like.  Some of the changes that have
occurred are presenting havoc on those of us who have used a mix of
applications, some Cygwin runtime and some Windows runtime.  This makes
it difficult as is evidenced by the complaints in this list about ACL
issues.

With the PATHEXT debate Michael (and others before him) is stating that
it would be nice if Cygwin, like its competitors, could use the PATHEXT
variable to determine if the file can be executed by extension.  The
naysayers are stating that it isn't POSIX or UNIX behavior; I agree with
that statement.  I don't agree that Cygwin cannot use this variable to
determine if a file is executable.  Cygwin doesn't have to determine the
program to use, the Windows API has the smarts for that.  All Cygwin
needs to do is to pass the file path to the API to execute the file.
Cygwin even now makes an exception for files ending in .exe; see the
output of 'ls -l /bin/ls' versus 'ls -l /bin/ls*'.

I've stated this to cast my support for using PATHEXT even if it is a
filtered option via the CYGWIN variable.  Michael are you willing to
provide code?

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