X-Spam-Check-By: sourceware.org Message-ID: <44CF8CD2.8070100@etr-usa.com> Date: Tue, 01 Aug 2006 11:18:10 -0600 From: Warren Young User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Cygwin-L Subject: Re: Revised: ls: reading directory .: No such file or directory References: <17370db50608010815ma1a27bfoac531286ad10d342@mail.gmail.com> <20060801155413.GA26030@trixie.casa.cgf.cx> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Andrew Schulman wrote: >> On Tue, Aug 01, 2006 at 09:15:44AM -0600, Monte Riding wrote: >>> I have an issue when trying to run ls in the root of my C: drive >>> that's cropped up recently, not sure what's happened - >> Morale of the story: Use POSIX paths, i.e. "cd /cygdrive/c". > > OK, but mightn't it be considered a bug that Cygwin is being inconsistent in > its treatment of non-POSIX paths? Would it make you happier if bash didn't accept DOS style drive letters at all? Then it would be consistent, and there would be no opportunity for confusion. The alternative is to do a lot of work across multiple apps. You name three, but if you think you're done with just that, you're in error. Down that path, you end up modifying all apps distributed with Cygwin to support DOS style paths. Ick cubed, dude. -- 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/