Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: dave DOT banham AT tde DOT alstom DOT com X-Lotus-FromDomain: GA To: Earnie Boyd cc: cygwin AT sourceware DOT cygnus DOT com Message-ID: Date: Tue, 10 Oct 2000 09:29:48 +0100 Subject: Re: BUG: Invalid assumption about file paths beginning with '\' Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Earnie, I would have thought that the whole point of the CygWin project was to provide UNIX tools on the PC Windows platform so that they feel like Windows tools and not like UNIX tools. In this respect the file system should work as expected for the platform on which the tool is used. The fact that CygWin is translating between the Windows file system and a UNIX/POSIX file system (to make the porting of UNIX tools to windows easier) is irrelevant since it is an internal (and abstracted) detail. An Example: If my working drive is m: and the current working folder is \projects (say) then when I execute: gwak -f \myscripts\script.awk in-file.txt I would expect gawk to read script.awk from m:\myscripts and in-file.txt from m:\projects. However, this results in a file not found for scripts.awk. If the command is modified to include the drive letter: gwak -f m:\myscripts\script.awk in-file.txt Then it works, which shows that CygWin correctly interpreted in-file.txt as being in the current working directory on the current drive. As I said in my original posting, I cannot explicitly state the drive letter on the command line as it is all part of a makefile which must be executable on any drive (since it is a network mapping). Regards Dave Banham -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com