X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:content-type
	:content-transfer-encoding:in-reply-to:references:date
	:message-id:mime-version; q=dns; s=default; b=UwLaALDV8DCVc092RC
	LF1AJo2x91JXuVgTKyUXxTPxQlpzLfBYL1Q8F2uC8uDxJdSz4jXFSLvtiv1xVktp
	v1Cvhsce0Ik0D9Krm+STjS7tt3ki+dQv7CUbNwnjluW+VEHXi8ixQ4hfDkraD0Zq
	+MH3Y4G0HzzfUycC/rcY/bnpg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:content-type
	:content-transfer-encoding:in-reply-to:references:date
	:message-id:mime-version; s=default; bh=J0u/mjYGXzQfG0DpYjKuuVWX
	Sds=; b=M1yF+2pBlhzdvm42ozUBfOzpY+Tkqpf9rJE0p/m2sd3Peb/6kgFWsHJg
	95wVMADTTaBixwefBC/eK3vWifduxuOszNxWHhW9lHsQSRkjqdVtzHG8U4YbkCe8
	A83veKtmekyhYFSjGciz9WjIdZ2AjODPCwQ4dcuwWIrVwbfvccY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=H*i:sk:40db60e, H*f:sk:40db60e, HImportance:Normal
X-HELO: mailout.ish.de
X-Abuse-ID: hremUFXL0y-8240@umkbw.customer
Anomaly-Results: submit.unitybox.de; rate=0%
Dubio-Filter: Adamant Filter v2016.04.1 submit.unitybox.de 3s7z3N5KPkz7t9S
From: Helmut Karlowski <helmut.karlowski@ish.de>
To: cygwin@cygwin.com
Cc: cygwin@cygwin.com
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by CYGWIN
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <40db60e7-cc96-d925-1d98-0a80be134d39@gmail.com>
References: <CACoZoo3_kBe6zWktTzydhHFzeZMr+AZe1Z2WujagTcLme_ctZg@mail.gmail.com> <40db60e7-cc96-d925-1d98-0a80be134d39@gmail.com>
Date: Tue, 9 Aug 2016 17:39:12 +0200
Message-Id: <20160809173912.78BF9E40.helmut.karlowski@ish.de>
MIME-Version: 1.0
X-IsSubscribed: yes

---------------------------------------------------
> file.  I'm not satisfied that we should continue with the .exe
> artificial symlink for the same reasons we shouldn't use PATHEXT.
> Because of the amount of time to port scripts and software to use the
> .exe suffix for executable files it should be an optional configuration
> that is on by default with a scheduled deadline (two or three years) to
> make it off by default.

Basically I'd agree. In this case any cygwin-prg that should be 
executable by windows would need a symlink to the .exe-version.

Or hook into windows' findfirst/findnext ;)
Would PATHEXT=%PATHEXT%;. be a good idea?

-Helmut


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

