> Here's a new one to add to that: Windows XP x64 uses *two*
> program files
> directories:
>
> C:\Program Files
> C:\Program Files (x86)
>
Oh God, they didn't.
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin
On Sat, 27 Aug 2005, Herb Martin wrote:
mount -fsb "c:/Program Files" "/pgf"
Agreed.
A common recommendation in the Windows world is to use C:\progra~1 which
is GENERALLY right but not totally reliable if either of the following
is true:
1) This is a second copy of Windows install
> [mailto:[EMAIL PROTECTED] On Behalf Of Brian Dessent
> Sent: Saturday, August 27, 2005 5:00 PM
> To: cygwin@cygwin.com
> Subject: Re: Spaces in Environment Variables
>
> Brian Dessent wrote:
>
> > $ export PF="/cygdrive/c/Program Files"
> > $ cd &quo
Brian Dessent wrote:
> $ export PF="/cygdrive/c/Program Files"
> $ cd "$PF"
And for the record, I find that it's a heck of a lot easier to do the
following once and then never have to deal with this kind of crap again.
mount -fsb "c:/Program Files" "/pgf"
Brian
--
Unsubscribe info: http:/
Jesse Hogan wrote:
> $ PF="/cygdrive/c/Program\ Files"
> $ export PF
> $ cd $PF
> : cd: /cygdrive/c/Program\: No such file or directory
> $ ls $PF
> ls: /cygdrive/c/Program\: No such file or directory
> ls: Files: No such file or directory
You are simultaneously overquoting and underquoting. Whe
-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 un
6 matches
Mail list logo
