Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Date: Fri, 15 Dec 2000 18:50:57 -0800
From: Stuart Smith <issmith@hmssoftware.com>
Subject: Bash Problems
To: cygwin@cygwin.com
Reply-to: issmith@hmssoftware.com
Message-id: <000001c0670b$0b098b90$970210ac@HMSISSMITH>
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal

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


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com