This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: bug in cygwin_conv_to_posix_path() caused by period in win32 path
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 4 Jul 2007 17:33:59 -0400
- Subject: Re: bug in cygwin_conv_to_posix_path() caused by period in win32 path
- References: <468A1024.8000007@mff.cuni.cz> <468A441A.2000009@cygwin.com>
- Reply-to: cygwin at cygwin dot com
On Tue, Jul 03, 2007 at 08:42:02AM -0400, Larry Hall (Cygwin) wrote:
> On 07/03/2007, Pavel Kudrna wrote:
>> >
>> >
>> > * /From/: "Dave Korn" <dave dot korn at artimi dot com>
>> >
>> > They are legal, but there's no possible way to convert them to POSIX,
>> which
>> > has no notion of a per-drive current directory.
>> > Ok, but Cygwin != POSIX :-)
>> Cygwin application has environment variable for each drive letter to
>> remember current drive. See example and run it from cmd.exe.
>
>
> And current drive != current directory on that drive.
>
> FWIW, the environment variables you speak of come from Windows. Cygwin
> doesn't use them.
Right. It does convert them to/from tne non-POSIX =X:= to the POSIX !X:=
but that is all that it does and all that it will do.
cgf
--
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/