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 Message-Id: <5.1.0.14.2.20020809055416.01fa03a0@pop3.cris.com> X-Sender: rrschulz@pop3.cris.com Date: Fri, 09 Aug 2002 05:57:39 -0700 To: Chris Game , cygwin@cygwin.com From: Randall R Schulz Subject: Re: cygwin and long filenames with spaces In-Reply-To: References: <20020808150914.GE6833@redhat.com> <20020808153224.GC8388@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Chris, It sounds like you have an alias or shell procedure standing in for the built-in "cd" command. What output does this command produce: type -a cd If it's not the built-in (i.e., the preceding command produces something other than just "cd is a shell builtin"), then make sure that alias or procedure is defined in such a way to tolerate spaces and meta-characters in its argument. Randall Schulz Mountain View, CA USA At 01:59 2002-08-09, Chris Game wrote: >In an earlier post, Christopher Faylor said... > > > You're doing it from bash. I assumed that the person was having > > problems from the command shell since they said "MS-Windows". But, > > on reflection, there is no guarantee that's the case here. Not enough > > info. > >I think I said 'bash' in the OP. > > > When there is a UNIX shell involved the quoting rules follow whatever > > the UNIX shell uses (as you know). When there is no UNIX shell involved > > then cygwin itself tries to do something halfway intelligent with the > > arguments. > > > > Anyway, with luck, one of our responses should have answered the > > question. > >Ha! (Sorry!) >Well, 'ls "/cygdrive/c/Program Files" ' works but 'cd >"/cygdrive/c/Program Files" ' doesn't! The message comes back: >bash: cd: /cygdrive/c/Program: No such file or directory > > >C. -- 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/