From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13917 invoked by alias); 9 Jul 2012 16:47:31 -0000 Received: (qmail 13898 invoked by uid 22791); 9 Jul 2012 16:47:27 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from mail1.multiplay.co.uk (HELO mail1.multiplay.co.uk) (85.236.96.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 09 Jul 2012 16:47:13 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Mon, 09 Jul 2012 17:46:27 +0100 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50020675813.msg for ; Mon, 09 Jul 2012 17:46:27 +0100 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=15377d4663=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: cygwin@cygwin.com Message-ID: <7918C4B87447499ABCE6066BDC0B4B47@multiplay.co.uk> From: "Steven Hartland" To: References: <20120709154456.GA6696@ednor.casa.cgf.cx> Subject: Re: Inconsistence on file operation when the name already exists with exe extension Date: Mon, 09 Jul 2012 16:47:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-07/txt/msg00122.txt.bz2 ----- Original Message ----- From: "Christopher Faylor" > On Mon, Jul 09, 2012 at 05:23:13PM +0200, notstop wrote: >>You must be right in some points, but that is not the exact behavior of >>windows command although you pretend it to be (the powershell has a >>different behavior). In fact, I can independently operate file while >>file.exe exists: >> >>copy file.exe file >>Now there are file and file.exe > > Nevertheless, FYI, powershell is not Cygwin and no one is saying that > the behavior you're seeing is mandated by Windows. What you are seeing > is a Cygwin accommodation for the fact that .exe is a special extension. > Cygwin is not a new project. Its handling of .exe has been hashed and > rehashed throughout the life of the project. The current behavior is > the compromise that we've settled on. This is a change which causes us pain regularly. The defaults in previous cygwin versions worked well and where predicatable from both a coding and user perspective. So we would have to agree with the author here that the current behavour should be reviewed and reverted to the much safer and more expected defaults where by only execution is a special case nothing more. > So, what you are seeing is expected. Continuing to argue without > familiarizing yourself with past discussions is not likely to expose > anything new. Take the example of a tar archive which has a windows .exe and say a Linux binary of the same name excluding the .exe. The current behaviour will have random results depending on the order of the files in the archive. So its likely that even though the archive extracted a working .exe file once the extract is actually complete the .exe will not be present. I appreciate that the idea was to make cygwin more internally consistent however surely predictable vs. random behaviour (as far as the user is concerned) is preferable is it not? Regards Steve -- 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