X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: David Bear <david DOT bear AT asu DOT edu>
Subject:  dealing with spaces in paths
Date:  Wed, 10 Jan 2007 18:18:35 -0700
Lines: 19
Message-ID:  <1278386.c5zxZe01gc@teancum>
Reply-To: david DOT bear AT asu DOT edu
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7Bit
Mail-Copies-To: david DOT bear AT asu DOT edu
User-Agent: KNode/0.9.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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?

-- 
--
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/