Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Originating-IP: [68.36.203.207] X-Originating-Email: [mrsouthern AT hotmail DOT com] From: "Mark Southern" To: Subject: Symlink implementation: support of shell links??? Date: Sun, 6 Apr 2003 18:06:27 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 06 Apr 2003 22:06:30.0674 (UTC) FILETIME=[C7268F20:01C2FC88] Correct me if i am wrong with any of this... Windows 98 thru XP ( with the .NET framework installed ) support shell links. These are different from shortcuts. A shell link is a folder ( with a couple of files inside it ) that points to another folder (ie a symlink). The benefit of this approach is that in shell link aware applications (such as windows explorer etc.) these show up as directories rather than shortcut (.lnk) files and enable browsing. As far as i can see, cmd.exe does not support shell links. For a better explaination of this see < http://www.pearlmagik.com/winbolic/ >. This is a great tool for creating shell links. My question for discussion is: should cygwin support shell links as directory symlinks or as mount points?? Mark. -- 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/