From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11743 invoked by alias); 9 Jul 2012 15:45:19 -0000 Received: (qmail 11694 invoked by uid 22791); 9 Jul 2012 15:45:16 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mho-01-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.71) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 09 Jul 2012 15:44:58 +0000 Received: from pool-173-76-45-230.bstnma.fios.verizon.net ([173.76.45.230] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1SoG8v-0006gP-RU for cygwin@cygwin.com; Mon, 09 Jul 2012 15:44:57 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id EBA3E4296BC for ; Mon, 9 Jul 2012 11:44:56 -0400 (EDT) X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+gAIYFz3kMGS4F1m6kYGzy Date: Mon, 09 Jul 2012 15:45:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Inconsistence on file operation when the name already exists with exe extension Message-ID: <20120709154456.GA6696@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00121.txt.bz2 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 Common email practice is to include the text of the email you are responding to so that we can know who you are accusing of "pretending". 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. So, what you are seeing is expected. Continuing to argue without familiarizing yourself with past discussions is not likely to expose anything new. -- 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