This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: Treatment of x:path again
- To: "'cygwin at sources dot redhat dot com'" <cygwin at sources dot redhat dot com>
- Subject: RE: Treatment of x:path again
- From: Stephan Mueller <smueller at microsoft dot com>
- Date: Mon, 16 Oct 2000 18:45:20 -0700
While it's true that you can ask cmd.exe for the current directory by using
something like echo %CD%, note that this is a pseudo-variable at best. It's
not found in older versions of cmd.exe (NT4SP3 or thereabouts being required
as a minimum) and it's clearly not a real variable: set without arguments
won't list it, and set cd=asdf will simply set a real variable to the value
asdf, and will have no effect on your current directory.
Or are you referring to something else?
stephan();
-----Original Message-----
From: Chris Faylor [mailto:cgf@cygnus.com]
Sent: Monday, October 16, 2000 6:37 PM
To: cygwin@sources.redhat.com
Subject: Re: Treatment of x:path again
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
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com