X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 19 Jun 2009 12:19:27 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: find(1) assertion for folder with a sub-folder named `x:' Message-ID: <20090619101927.GV5039@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <83k5381ra3 DOT fsf AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83k5381ra3.fsf@gmail.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 Jun 19 17:55, Haojun Bao wrote: > hi, > > Here's a test case to make find(1) assertion: > > mkdir no-such-dir/foo/bar: -p > > #this will not assert > find no-such-dir/ > > mkdir no-such-dir/foo/c: -p I think the right answer here is "don't do that". Don't create files or directories starting with a single character, followed by a colon. The problem is that a path starting with "X:" is treated as an absolute Win32 path. Right now you cannot have both. Either a path starting with "X:" is treated as Win32 path, or Cygwin must stop handling Win32 paths at all and only allow POSIX paths. 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/