This is the mail archive of the
mailing list for the Cygwin project.
Re: Problem with dereference option on Windows LNKs (shortcuts)
- From: "Max Bowsher" <maxb at ukf dot net>
- To: "Mellem, Dan" <Dan dot Mellem at pomona dot k12 dot ca dot us>,<cygwin at cygwin dot com>
- Date: Mon, 14 Jul 2003 22:07:49 +0100
- Subject: Re: Problem with dereference option on Windows LNKs (shortcuts)
- References: <4B8A0478615FD3118F1600508B0BB71B02F61ACA@pusd-mail.pusd.org>
Mellem, Dan wrote:
> From: Igor Pechtchanski On: 7/12/03 6:05 PM
>> Cygwin symlinks are a bit more than read-only shortcut (.lnk) files.
>> They have a special format, and they also have something in their
>> "Comment" field (that you can check via shortcut properties). In short,
>> you cannot easily create a Cygwin symlink from outside Cygwin. For
>> exact details, see the source of the symlink() function in
> Thanks, Igor. I thought that since it created MS-Windows-compatable .LNKs,
> it also read regular .LNKs and used them as symlinks.
> I took a look at the source
> oot=src) but didn't find anything specific that said that they aren't
> treated as symlinks. I'm not familiar with the source but there was a
> I don't know what this all means but it implies to me that it will at
> attempt to read the shortcut file. Is it possible to parse through regular
> shortcut files too?
Possible to write code to do this? Yes, of course, but probably not
desirable, see below.
Possible to set an option to cause this? No, not currently, and probably
Importantly, a Cygwin symlink contains a *POSIX* path. The fact that the
symlink is also a windows shortcut is essentially just decoration.
Obviously, a normal shortcut does not contain a POSIX path. It would
probably be possible to deduce one, but there are good reasons for not doing
so: Extra data (icon, etc.) would be removed when shortcuts were saved and
restored with tar, for example.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html