X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: David Bear Subject: Re: dealing with spaces in paths Date: Wed, 10 Jan 2007 21:23:39 -0700 Lines: 38 Message-ID: <3445035.yTEPPvuVV4@teancum> References: <1278386.c5zxZe01gc@teancum> <45A5AA85.1040204@cygwin.com> Reply-To: david.bear@asu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Mail-Copies-To: david.bear@asu.edu User-Agent: KNode/0.9.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Larry Hall (Cygwin) wrote: > David Bear wrote: >> I'm attempting to script building mount points in order to handle spaces >> in file names. So I do something like this: >> >> homedir=`cygpath -w $USERPROFILE` >> mount -buf "\"$homedir\" $HOME/myh >> >> When I echo the mount command to the syntax looks correct. >> >> However, when I actually run the mount command via the script I get the >> message there are not enough parameters, like mount is not getting what >> it needs. >> >> Dealing with spaces is a huge pain... but this seems be one way to handle >> them. Any idea why mount is unhappy when scripted as shown above? >> > > Quote $USERPROFILE. Loose the '\'s around $homedir. Make sure that there > is only 1 quote preceding $homedir. > since the homedir does have spaces in it, you need to enclose it in quotes to prevent mount for assuming that each separate word in the path is a new mount point. There is a sample of it at http://comments.gmane.org/gmane.os.cygwin/54674 the \" escapes the " so that it is passed through to the command line the script generates. when I leave out the quotes -- I get multiple lines and multiple errors from the script. -- -- David Bear College of Public Programs at Arizona State University -- 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/