Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <38298502.66A607C5@agames.com> Date: Wed, 10 Nov 1999 06:45:22 -0800 From: "David O'Riva" Organization: Atari Games, Inc. X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Halim, Salman" CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re: resolving symbolic links References: <512EBEF97F02D311B89900A0C9D1776009D590 AT thor DOT operations DOT bluestone DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Halim, Salman" wrote: > > what's a good way to find out (programmatically; either through a command or > a piped series of commands or a function), in bash (if relevant), the actual > path pointed to by a symbolic link. for example, i have /tmp pointing to > c:\temp -- how can i get 'c:\temp' as output given '/tmp' as input? i > thought of ls -al /tmp | cut -d'>' -f 2- but that seems a bit of a kludge. . > Specifically for cygwin, you can use "cygpath -w /tmp". Very handy for using ancient editors ( function q { \q `cygpath -w $*` ; } ) -- -dave _________________________ ------------/ David O'Riva \-------------- 408- | Staff Software Engineer | oriva@ 473-9413 | Atari Games, Inc. | agames.com \_________________________/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com