From: condict@opengroup.org (Michael Condict) Subject: Re: Picking up include directories automatically 23 May 1997 20:48:31 -0700 Sender: mail@cygnus.com Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <199705212123.RAA13147.cygnus.gnu-win32@postman.opengroup.org> X-Authentication-Warning: postman.opengroup.org: Host hare.osf.org [130.105.7.99] didn't use HELO protocol Original-To: "Mikey" <*jeffdb@netzone.nospam.com> Original-cc: "JP Shipherd" , "cygnus gnu-win32 mailing list" , condict@opengroup.org In-reply-to: Your message of "Mon, 19 May 1997 12:22:01 PDT." <199705210042.RAA21924@nz1.netzone.com> Original-Sender: owner-gnu-win32@cygnus.com In message <199705210042.RAA21924@nz1.netzone.com>, you write: > How about putting export /c/dir because you mounted c:\\ to /c > which was my point in the first place YOU DON'T NEED // Exactly. Or you could just use "export /dir", if you've mounted c: under /, which is the default, after all. But the mount command doesn't mind that you mount c: twice, once under / and again under /c. I've done this for consistency. Also, whenever I want to refer to a networked drive, I mount it somewhere first. Usually I just mount the drive letter I've mapped it to: mount g: /g In any case, I agree 100% with you that "//" is dangerous because any UNIX program that notices it will think it's equivalent to "/" and may feel free to delete one of the slashes. For similar reasons "c:/..." paths are dangerous. Unix programs will assume that this is a relative pathname, not an absolute one, and may even create files in the wrong place. The other reason I never use "//" or "c:/" paths is that bash can't do file-name completion on such names. This is a fixable bug, I guess, but why bother. Michael Condict m.condict@opengroup.org The Open Group Research Inst. (617) 621-7349 11 Cambridge Center Cambridge, MA 02142 - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".