RE: using Windows links

[Mellman Thomas <Thomas dot Mellman at icn dot siemens dot de>]

>>-----Original Message-----
>>From: Larry Hall (RFK Partners, Inc) [mailto:lhall@rfk.com]
>>Sent: Tuesday, April 30, 2002 4:17 PM
>>To: Mellman Thomas; cygwin@cygwin.com
>>Subject: Re: using Windows links
>>>An interesting side effect: I have a shortcut (Desktop.lnk) 
>>on my $HOME
>>>that was originally created by Windows.  I can't cd there 
>>anymore.  I tried
>>>to create a second link for Cygwin (Desktop), but ln tells 
>>me it already
>>>exists!
>>>
>>>$ ln -s $nt/Desktop Desktop
>>>/bin/ln: creating symbolic link `Desktop' to 
>>`/cygdrive/c/WINNT/Profiles/mt099378/Desktop': File exists
>>>
>>>Thus, even though Desktop.lnk isn't recognized as anything 
>>special, it
>>>is anyway!
>>
>>
>>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.

Thus, cygwin is throwing in the towel on link/Shortcut compatibility, but I think it was forgotten to remove some of the code.

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?


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