Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C0FEDC1.BD4C0E14@verizon.net>
Date: Thu, 06 Dec 2001 14:14:25 -0800
From: David Rothenberger <d DOT roth AT verizon DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ryan T. Sammartino" <ryants AT shaw DOT ca>
CC: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.3.6-3 and xemacs
References: <Pine DOT WNT DOT 4 DOT 33 DOT 0112060937500 DOT 1404-100000 AT MSD-PC3> <20011206154936 DOT GA22573 AT redhat DOT com> <20011206175147 DOT GB28243 AT localhost> <3C0FCB23 DOT 2EDCC0B0 AT verizon DOT net> <20011206203538 DOT GA28805 AT localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think it's related.  My little test program shows that when
cygwin_posix_to_win32_path_list() is called with "/cygdrive", it also
returns an empty string.  Strangely, "/cydrive/" returns "\".

I have no idea why xemacs is calling the function with "/cygdrive" when
following symlinks like the ones you described, but it does.

Maybe cgf can fix this behavior, too...

Dave

"Ryan T. Sammartino" wrote:
> 
> On Thu, Dec 06, 2001 at 11:46:43AM -0800, David Rothenberger wrote:
> > I've done a little debugging and here's what I've found out.
> >
> > It appears to be a problem/change to the behavior of
> > cygwin_posix_to_win32_path_list().  When this function is called with a
> > path of the form "/cygdrive/z/something", it returns an empty string
> > unless the drive "z" actually exists.  This seems incorrect to me, since
> > this function always returns a valid Windows path for other POSIX paths,
> > even if the file or directory doesn't actually exist.
> >
> > Even more troubling, the function appears to return garbage when called
> > with "/cygdrive/z" or "/cygdrive/z/", unless "z" is a valid drive.
> >
> 
> I dunno if that is related to the problem I'm having.  I'm trying to
> open a file like ~/project/foo, and ~/project is a symlink to
> /cygdrive/d/project, and drive D certainly exists for me.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/