Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-Id: <200501172317.j0HNHfg16996@networking.Stanford.EDU>
Subject: Re: odd behavior of symlinks on Win XP SP2
To: cygwin@cygwin.com
In-reply-to: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com> 's message of Mon, 17 Jan 2005 17:07:56 -0500
Reply-to: Jeff.Hodges@KingsMountain.com
From: Jeff.Hodges@KingsMountain.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 17 Jan 2005 15:17:41 -0800

skoehler@upb.de said:
> He clearly complained about MS-Software that  cannot handle
> cygwin-created links, and you're talking about cygwin  understand its
> own symlinks

correct. thanks.


cgf-no-personal-reply-please@cygwin.com said:
> Apologies.  I took the word "altogether" to mean "completely" but
> obviously missed the meaning implied by "from the windoze
> perspective".

accepted & understood. thanks.


So, again, from the perspective of having cygwin-created symlinks that 
transparently behave as windows shortcuts, they (cygwin-created symlinks) are 
presently half-broken on XP.  And if MSFT were to for some reason align their 
explorer code to match their Open-Save dialog code wrt how they treat (and 
discriminate between) shortcuts, cygwin-created symlink/shortcuts would likely 
quit working entirely *in the windows world* (they'd of course likely to 
continue to work fine in the cygwin world). If this were to come to pass and 
not be addressed by the cygwin community, then it wouldn't make any sense to 
have the the default (or even option) of creating cygwin symlinks as 
"winsymlinks". This would be a loose, imv.

thanks,

JeffH


--
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/