Mail Archives: cygwin/2002/05/02/10:53:37
>>> >>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/
- Raw text -