X-Spam-Check-By: sourceware.org Date: Tue, 11 Jul 2006 10:49:26 -0700 From: George To: cygwin@cygwin.com Subject: Re: Cgywin filename with 255 character Message-ID: <20060711174925.GA1440@home> 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.4.2.1i X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk 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 On Tue, Jul 11, 2006 at 06:01:40PM +0200, J"org Schaible wrote: > Hi Larry, > > Larry Hall (Cygwin) wrote on Tuesday, July 11, 2006 4:50 PM: > [snip] > > Windows places a limit on the number of ASCII characters in a > > file/path name. It's approximately 260 characters. Cygwin path > > conversion may cut that down a bit. > > Is there any pointer at MS, where this is described exaclty? I was > only able to find some entries in the knowledge base that describe > applications that are affected by this limit, but nowhere an > explanation under what circumstances a process/application is hit by > this limit. You could also try yesterday's article at http://it.slashdot.org/article.pl?sid=06/07/10/1238246 for some vaguely wrong but occasionally inspired opinions on the subject, at least written in a language less terse than that typically found in most Microsoft documentation. YMMV. -- George +1 Informative -- 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/