delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/03/05/13:14:37

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3AA3D37F.7A7BCDDA@veritas.com>
Date: Mon, 05 Mar 2001 09:57:19 -0800
From: Bob McGowan <rmcgowan AT veritas DOT com>
Organization: VERITAS Software
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: New symlinks.
References: <17B78BDF120BD411B70100500422FC6309E220 AT IIS000> <200102281857 DOT UAA05162 AT linux.> <20010228183811 DOT B5603 AT redhat DOT com> <200103021239 DOT OAA03969 AT linux.> <3AA00EF1 DOT 8F172E6C AT digitalfocus DOT com> <200103031723 DOT TAA20710 AT linux.>

The shortcut does work, but only in a limited way.  The browse functionality in an "Open File" dialog works, so long as you double click on the shortcut.  The "Run->Browse"
treats the shortcut as a file and attempting to use the shortcut name in a path specification where the shortcut is in "the middle", results in an "invalid path" error. 
This also applies to trying to use the shortcut name in a 'cd' command from a "DOS" prompt, either by itself or as part of a longer path specification, or for typing in a
path specification in the browse window's filename field.

Double clicking on the shortcut name in Explorer also works, moving to the directory pointed to by the shortcut, but the shortcut name only shows up in the right hand
window, since it is not a directory.

Ehud Karni wrote:
> 
> On Fri, 02 Mar 2001 16:21:54 -0500, Daniel Barclay <Daniel DOT Barclay AT digitalfocus DOT com> 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.
> 
> I guess in both. I checked by giving a path to 1: the built in "run"
> (BTW with its "browse" you can't even traverse the link). 2: as file
> to open to `notepad' and other native M$ windows utilities.
> 
> BOTH FAILED !
> 
> Ehud.
> 
> --
>  @@@@@@ @@@ @@@@@@ @    @   Ehud Karni  Simon & Wiesel  Insurance agency
>      @    @      @  @@  @   Tel: +972-3-6212-757    Fax: +972-3-6292-544
>      @    @ @    @ @  @@    (USA)  Fax  and  voice  mail:  1-815-5509341
>      @    @ @    @ @    @        Better     Safe     Than     Sorry
>  http://www.simonwiesel.co.il    mailto:ehud AT unix DOT simonwiesel DOT co DOT il
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan AT veritas DOT com

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019