X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <1276042636 DOT 1651 DOT 9 DOT camel AT erebor> <20100609044034 DOT GB9305 AT ednor DOT casa DOT cgf DOT cx> Date: Wed, 9 Jun 2010 12:39:10 +0100 Message-ID: Subject: Re: 'cp' utility bug when .exe file exist. From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 9 June 2010 10:48, Julio Costa wrote: >>>And this is where my head got reeeally spinning... can anyone, please, >>>explain the reason to why this .exe magic exists, anyway? As far as I understand it, the original reason for it was that Windows 9x always required it. Of course Cygwin 1.7 no longer supports 9x, so from that perspective, it's no longer needed. >> [Running in cmd.exe] > The point is, that *is not* a reason, because it is easily fixed by > "set PATHEXE=%PATHEXE%:.". That's a nice one. I certainly didn't know about that. Explorer still needs the .exe though. More importantly, a lot of build scripts likely depend on the .exe being added automatically. The frequent questions and problems around this issue do make me wonder though whether it wouldn't indeed be better to drop the .exe magic completely, deal with the ensuing pain, but eventually be done with it. Andy -- 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