dealing with spaces in paths
Larry Hall (Cygwin)
Thu Jan 11 15:22:00 GMT 2007
David Bear wrote:
> 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
> 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.
That's why I said to quote USERPROFILE. I guess I should have included my
version of your script, which worked fine for me:
homedir=`cygpath -w "$USERPROFILE"`
mount -buf "$homedir" "$HOME"/myh
This is recreated from memory because I don't have access to Cygwin now.
But this is essentially what worked fine for me last night. Note, the
quote around USERPROFILE is important.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin