X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 26 Feb 2009 22:21:22 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Another long pathname question Message-ID: <20090227032122.GA12058@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090226233547 DOT GA27105 AT ednor DOT casa DOT cgf DOT cx> <200902270232 DOT n1R2W0pw032436 AT mail DOT pdinc DOT us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200902270232.n1R2W0pw032436@mail.pdinc.us> User-Agent: Mutt/1.5.16 (2007-06-09) 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 Thu, Feb 26, 2009 at 09:33:07PM -0500, Jason Pyeron wrote: >> From: cygwin-ownerX Oh! Is that who it came from? >> [mailto:cygwin-ownerX Yes. Got that the first time. >> Sent: Thursday, February 26, 2009 18:36 Hmm. It's 10:18PM here. >> To: cygwinX What? You're responding to email to the mailing list? Oh, wait. This is the mailing list. >> Subject: Re: Another long pathname question Is that an echo? >> On Thu, Feb 26, 2009 at 02:29:57PM -0500, Greg Freemyer wrote: >>>If the path is short, it uses the full long directory name as expected. >>>If the path exceeds 260, it reverts to using the 8.3 names, thus giving >>>a workaround that will allow you to descend deeper into a directory >>>structure. >>> >>>Interesting trick. Maybe you should consider something similar for >>>cygwin. > >I read this as: When launching a non aware application..., silly me. I read this as you not understanding that we don't want to add hacks to accommodate uncommon corner cases which slow down Cygwin's path processing. Clever me. cgf -- 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/