Date: Mon, 9 Jul 2012 11:44:56 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT 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 AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <BLU0-SMTP193F74A0A7FC396B8160663CED30 AT phx DOT gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BLU0-SMTP193F74A0A7FC396B8160663CED30@phx.gbl>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

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