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: Fri, 9 Aug 2002 12:10:40 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin and long filenames with spaces Message-ID: <20020809161040.GC14475@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020808150914 DOT GE6833 AT redhat DOT com> <20020808153224 DOT GC8388 AT redhat DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020809055416 DOT 01fa03a0 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Fri, Aug 09, 2002 at 05:06:58PM +0100, Chris Game wrote: >In an earlier post, Randall R Schulz said... > >> 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. > >Ah! That vaguely rings a bell. > >Yes, long ago in the days of beta 19.whatever I must have set cd up >as a function including a 'pwd' line. The response is: > >cd is a function >cd () >{ > builtin cd $1; > pwd >} >cd is a shell builtin > >So - I need to modify the 'builtin ...' line. > > > >Well, 'builtin cd "$*";' works! No idea if that's the correct >modification though. It's *a* modification, at least. That would actually allow you to do something like: cd /cygdrive/c/Program Files without the quotes. cgf -- 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/