Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-Id: <5.1.0.14.2.20020401164229.029cf138@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Mon, 01 Apr 2002 16:48:00 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: bash & filenames with spaces In-Reply-To: <4.3.1.2.20020401192733.025e28f8@pop.ma.ultranet.com> References: <20020401191544 DOT A616 AT isis DOT thalatta> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Larry, I don't think the mount table can account for the diagnostic that Will reported. My guess would be that there's a shell procedure defined called "cd" and it was not written to accommodate arguments with spaces. Randall Schulz Mountain View, CA USA At 16:31 2002-04-01, you wrote: >At 07:15 PM 4/1/2002, Will Parsons wrote: > >Bash won't allow me to cd to a directory with a space in it. The FAQ > >implies that all that is necessary is to escape the space, but whether > >I type (e.g.): > > > >cd /c/Program\ Files > > > >or > > > >cd '/c/Program Files' > > > >I get a message: > > > >cd: Program: No such file or directory > > > >Am I missing something obvious here? > > >You're missing something but it's not obvious what it is. Try a few >variations on this, seeing if you can eliminate things like the mount >table and so on. Perhaps you want to run strace on bash to see if you can >see where it has trouble. Looking at the output of cygcheck -s -r -v >might help too. > > >Larry Hall -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/