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 Date: Mon, 1 Apr 2002 20:43:44 -0500 From: "William B . Parsons" To: cygwin AT cygwin DOT com Subject: Re: bash & filenames with spaces Message-ID: <20020401204344.A509@isis.thalatta> References: <20020401191544 DOT A616 AT isis DOT thalatta> <4 DOT 3 DOT 1 DOT 2 DOT 20020401192733 DOT 025e28f8 AT pop DOT ma DOT ultranet DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020401164229 DOT 029cf138 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <5.1.0.14.2.20020401164229.029cf138@pop3.cris.com>; from rrschulz@cris.com on Mon, Apr 01, 2002 at 19:48:00 -0500 Lines: 50 On 2002.04.01 19:48 Randall R Schulz wrote: > 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. How embarassing. There in my .bashrc file (which I had taken from a Unix system) I had cleverly (?) defined: cd () { command cd $1 pwd } And of course I had never noticed the bug in Unix... Thanks to all who replied. > 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. -- 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/