X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 7 Apr 2009 09:54:19 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: edit Aux.pm under GNU emacs hangs Message-ID: <20090407075419.GB20277@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <22909185 DOT post AT talk DOT nabble DOT com> <5E25AF06EFB9EA4A87C19BC98F5C875302FBD5C5 AT core-email DOT int DOT ascribe DOT com> <20090406161239 DOT GA12558 AT trikaliotis DOT net> <20090406162026 DOT GA8063 AT calimero DOT vinschen DOT de> <49DA549A DOT 4090208 AT veritech DOT com> <20090406200700 DOT GS852 AT calimero DOT vinschen DOT de> <49DA9B3A DOT 1010309 AT veritech DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49DA9B3A.1010309@veritech.com> User-Agent: Mutt/1.5.19 (2009-02-20) 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 Apr 6 20:15, Lee D.Rothstein wrote: > Corinna Vinschen wrote: >> On Apr 6 15:14, Lee D. Rothstein wrote: >>> Corinna Vinschen wrote: >>>> http://cygwin.com/1.7/cygwin-ug-net/using-specialnames.html >>>> >>> Can't have any files named [aA][uU][xX] dot *anything* in Windows, or >>> anything dot [aA][uU][xX]. >> >> Incorrect. This is a restriction in the Win32 API, it's not a >> restriction of the filesystem or the native NT API which Cygwin 1.7 uses >> for file access (almost) exclusively. > > The specific problem symptoms that the original poster mentioned, I was > able to > replicate WITH a windows app, which seems to me indicates that he was > using a win32 app, i.e., > GNU emacs for Win32? > > I apologize for my oversight and I certainly wasn't criticizing you, in > any way! No worries. I didn't feel criticized. Maybe we were just talking of two different things. My point is that this isn't a generic problem on Windows, just a DOS backward compatibility weirdness on the Win32 level. That's why Cygwin 1.7 applications won't have that problem. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/