* Brian Dessent (Tue, 01 May 2007 12:25:15 -0700) > Thorsten Kampe wrote: > > What about this "winsymlinks" Cygwin environment variable? The > > description says "if set, Cygwin creates symlinks as Windows shortcuts > > with a special header and the R/O attribute set. If not set, Cygwin > > creates symlinks as plain files with a magic number, a path and the > > system attribute set. Defaults to set". > > > > So why don't the symlinks "work" under Windows (despite being "created > > as Windows shortcuts with a special header")?? > > They do work, in Explorer. Or in common dialogs, like file-open, > file-save-as, etc. But CMD.EXE doesn't know anything about Explorer > shortcuts, so it will never do the right thing.
I can't confirm that: I've created a shortcut to setup.exe and started the link called setup.lnk in cmd.exe and setup.exe was started. The same with a command line program. -- 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/
