Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3AA00EF1.8F172E6C@digitalfocus.com> Date: Fri, 02 Mar 2001 16:21:54 -0500 From: Daniel Barclay X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: ehud@unix.simonwiesel.co.il CC: cygwin@cygwin.com Subject: Re: New symlinks. References: <17B78BDF120BD411B70100500422FC6309E220@IIS000> <200102281857.UAA05162@linux.> <20010228183811.B5603@redhat.com> <200103021239.OAA03969@linux.> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ehud Karni wrote: > ... > The real problem of Windows .lnk files (within Windows use) is that > even though you can make link to a directory, you can not really use > it. Unlike UNIX, you can not use .lnk files as middle part of path, > it may only be used as the terminating part (basename) of a path. Why not? Or, probably, "where not"? In the Window UI, you can have links (shortcuts) to directories. Conceptually, these are in the middle part of a path (the virtual path you tranverse step by step in the UI). Are links not usable in the middle of pathnames given to the command-line interpreter? Or are links not usuable in pathnames given to Windows OS calls for file operations. Daniel -- Daniel Barclay Digital Focus Daniel.Barclay@digitalfocus.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple