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
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <BE684E2C997AD51199530002A56B20796C3644@MCHH2A1E>
From: Mellman Thomas <Thomas DOT Mellman AT icn DOT siemens DOT de>
To: "'Larry Hall (RFK Partners, Inc)'" <lhall AT rfk DOT com>, cygwin AT cygwin DOT com
Subject: RE: using Windows links
Date: Thu, 2 May 2002 16:53:06 +0200 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"

>>> >>Just because it isn't recognized as a Cygwin symbolic link 
>>> >>doesn't mean it
>>> >>doesn't exist as a file as far as Cygwin is concerned.
>>>
>>>
>>>
>>>The thing is, the Windows-created Shortcut is called 
>>Desktop.lnk and I'm trying to create simply Desktop.  There 
>>is NO file called Desktop.  But ln(1) fails, telling me that 
>>Desktop exists.
>>
>>
>>Cygwin symlinks, by default, create windows shortcuts.  
>>Windows shortcuts 
>>append ".lnk" onto the name of the file given as the 
>>shortcut.  So you may
>>think you're asking Cygwin to create "Desktop" but you're 
>>actually asking 
>>it to create "Desktop.lnk".  


Hmmm.  Consider this:

$ ln -s /h  h
$ lf
Desktop@  h@
$ ll h
lrwxrwxrwx    1 Administ Kein           85 May  2 14:46 h -> /h
$ 

There's no h.lnk here.
Is this just a question of having the right frame-of-mind?


>>
>>>Thus, cygwin is throwing in the towel on link/Shortcut 
>>compatibility, but I think it was forgotten to remove some of 
>>the code.
>>
>>
>>Wrong on both accounts.  The default Cygwin symbolic link 
>>creation mode 
>>makes shortcuts.  These shortcuts are usable directly by 
>>Explorer and other
>>Windows apps that understand Windows shortcuts.  Shortcuts 
>>made by Windows
>>are not grokked as Cygwin shortcuts however.  There's nothing 
>>"wrong" here.


I didn't use the word "wrong".  I only said, "non-compatible".



>>>Hmmm.  Theoretically, I should fix this myself.  If I were 
>>able to right now (unfortunately, I don't think now is the 
>>right time), how could I contribute here?  I'd have to get 
>>all the source for cygwin1.dll, configure my machine for 
>>remote CVS access, find and make the change, and then?  What 
>>would be next?
>>
>>Start here: www.cygwin.com/contributing


Thank you for the link.

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