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: <4310DE6C.20305@byu.net> Date: Sat, 27 Aug 2005 15:43:08 -0600 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Jesse Hogan CC: cygwin@cygwin.com Subject: Re: Spaces in Environment Variables References: <20050827213817.79719.qmail@web52805.mail.yahoo.com> In-Reply-To: <20050827213817.79719.qmail@web52805.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Jesse Hogan on 8/27/2005 3:38 PM: > If I set environment variables to paths that have > spaces in them they don't work right with common shell > commands. Does anybody know a work around for this? Read up on shells; this problem is not unique to cygwin (although cygwin tends to be more likely to expose it, since Windows is more likely to have spaces in filenames). Bash splits words on spaces after expanding variables, unless the variables are double quoted. > $ cd $PF cd "$PF" - -- Life is short - so eat dessert first! Eric Blake ebb9@byu.net volunteer cygwin bash maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDEN5s84KuGfSFAYARAlf4AJ9IF5xvUpbaCJD/+q2unbBxaXCiKwCggDr0 B93BmvBkUwnkNKTMPDbzsdo= =ymnC -----END PGP SIGNATURE----- -- 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/