Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Herb Martin" To: Subject: RE: Spaces in Environment Variables Date: Sat, 27 Aug 2005 19:02:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <4310E262.8999464A@dessent.net> Message-ID: X-Sign-LQC: HerbM AT learnquick DOT com/2005-08-27 19:02:32/=rshpggfc > [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Brian Dessent > Sent: Saturday, August 27, 2005 5:00 PM > To: cygwin AT cygwin DOT com > Subject: Re: Spaces in Environment Variables > > 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" 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 installed where an older C:\Progra~1 already existed -- and so we have c:\progra~2 etc. 2) Short names have been disabled (and of course if the Program Files aren't on the C:\ drive path.) My practice (even under pure) Windows is to always setup an alternative path with "linkd". This is effectively the same principle as just going ahead and fixing it with your "mount" suggestion. Thanks for the good suggestion. -- Herb Martin -- 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/