Message-ID: <45A5BF06.6020602@gmail.com>
Date: Wed, 10 Jan 2007 21:37:26 -0700
From: Morgan Gangwere <0 DOT fractalus AT gmail DOT com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: re: dealing with spaces in paths
OpenPGP: id=5231E2FA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


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?
> >
because you are feeding mount a path like /boo/some stuff/ like mount
/boo/some stuff. unfortunately this is because you need quotes around
that path.
here's what i think your trying to run:
mount /cygdrive/c/documents and settings/$UNAME/
this will cause mount to think its bring run with the hooks
?/cygdrive/c/documents
?and
?settings/$UNAME/

run something like mount "/cygdrive/c/documents and settings/"$UNAME"/"
and it should work...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)

iD8DBQFFpb8GXIyDjlIx4voRAsmOAJoD3MTTSMozlvCxNZLjLm1Ne7wR5QCgmJs5
fthMBl+mfxyWtjX1tdfZiS4=
=rHkF
-----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/