DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=ARf3mxIMwYio6yxm
	wdGLDhjMeQcl6tCWZsEu2WHMapMGG0k3uo1R8QhOpXxpc3+QHkVvYCVaLiKNJY0v
	gTElq3FUjVDCTDXYGWRzxeCKQcuGSLPBfQh9a2e5oAA609TWVEWtwnyp/KxeqAJC
	GimwF76ti8B8/qtCNyWQWW0Sp8s=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 11 Aug 2016 00:05:39 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1546760683.20160811000539@yandex.ru>
To: =?windows-1252?Q?Hans-Bernhard_Br=F6ker?= <HBBroeker@t-online.de>,
        cygwin@cygwin.com
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by CYGWIN
In-Reply-To: <3bed7d1a-1747-5dd9-6dea-594588006000@t-online.de>
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>  <3bed7d1a-1747-5dd9-6dea-594588006000@t-online.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

Greetings, Hans-Bernhard Bröker!

> Am 10.08.2016 um 03:01 schrieb Andrey Repin:

>> PATHEXT tells the shell to consider these file extensions executable.

Erik:
> PATHEXT is very simply a list of extensions CMD.EXE will automatically
> append to the given filename when searching the PATH for a command to
> execute.  Once a filename+extension is found, CMD.EXE still needs to
> know what to do with the given file to be able to execute it.

Hans:
> No.  That's what file associations do.  cygstart will apply those where 
> needed, so let's consider that aspect of the case closed, shall we?

> PATHEXT has just _one_ job, in those few tools that even use it: it 
> saves one the burden of referring to a file by its actual name.  It's 
> what makes a given command of just

Yes, sorry. I was slightly confused myself.
I rechecked my facts afterward, and, indeed, cmd was successful in executing a
script through file association, given the name including extension, even
though I explicitly removed the extension from PATHEXT and respawned the
shell to be absolutely sure.

The point about <Tab>'ing of course makes PATHEXT less and less appealing in
its native form.


-- 
With best regards,
Andrey Repin
Thursday, August 11, 2016 00:01:14

Sorry for my terrible english...