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 Message-Id: <4.3.1.2.20001216131312.020f7e80@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 16 Dec 2000 13:15:48 -0500 To: issmith AT hmssoftware DOT com, cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Bash Problems In-Reply-To: <000001c0670b$0b098b90$970210ac@HMSISSMITH> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 09:50 PM 12/15/2000, Stuart Smith wrote: >Hi, > >I have just downloaded and installed cygwin 1.1.6 in replacement for B19 and >I seem to have found a significant difference that I am not sure should be >there. In version B19, I could invoke the cygtclsh80 application and send in >a file name including a fully qualified path (for example, cygtclsh80 >//c/foo/bar/mytclscript.tcl). In this particular case the path for the file >was being obtained by the pwd command and all seemed to function correctly. > >Having install 1.1.6, I find that the pwd command returns the same >information, but the cygtclsh80 nolonger can decipher the directory path and >hence find the file. If I was to move to the //c/ directory and issue the >command manually without the //c/ then all seems to be OK. The version of >cgytclsh80 is 8.0.4 > >Does anyone have any ideas ?? > >Stuart Smith // syntax is deprecated. See the FAQ entry at www.cygwin.com titled "How can I access other drives?" for info on valid paths formations to see if that helps. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com