Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Chris Faylor Date: Mon, 16 Oct 2000 21:36:47 -0400 To: cygwin@sources.redhat.com Subject: Re: Treatment of x:path again Message-ID: <20001016213646.B8167@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <20001016115319.C11579@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: ; from Lassi.Tuura@cern.ch on Tue, Oct 17, 2000 at 03:31:19AM +0200 On Tue, Oct 17, 2000 at 03:31:19AM +0200, Lassi A. Tuura wrote: >|> How would you suggest having something be 'relative to the current path' >|> in cygwin, given the /cygdrive method of doing things? cygwin has never >|> kept track of the current directory of other drives. > >FWIW, it seems this isn't even possible under Win32. Based on MSDN docs >it sounds like Win32 maintains only one current directory and really >knows nothing about disk drives in that context. It is only cmd.exe >that maintains an illusion of a current directory for all the drives on >Windows NT and 2000. NT stores the current directory in environment variables, actually. Windows 9x seems to store the information at the OS level. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com