X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20100915140721.GS15121@calimero.vinschen.de> References: <20100915120315.GQ15121@calimero.vinschen.de> <20100915135030.GR15121@calimero.vinschen.de> <20100915140721.GS15121@calimero.vinschen.de> Date: Wed, 15 Sep 2010 18:23:47 +0200 Message-ID: Subject: Re: .exe magic reloaded 2 From: Al To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com > > For instance, this one: =A0Either we always remove the .exe suffix from > a file, or we have to check for each file with a .exe suffix, whether > it's executable or not. Probably without checking it. No sane program would use the .exe suffix as extension of a mere textfile. What would be the ideal approach, without thinking of backward issues? How about this? 1.) When a file is made executable .exe is appended, but only visible from Windows API. 2.) When the last execution bit is removed the .exe suffix is also removed. 3.) Using the .exe suffix from the Cygwin API always gives an error. 4.) Hence: You never see this suffix on the Cygwin API. Al -- 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