From: CDavey@or.cadix.com (Colin Davey)
Subject: can't invoke tclsh with filename like //e/foo/bar...
10 Jul 1997 20:38:55 -0700
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <c=US%a=_%p=CADIX_Internatio%l=KIRIN-970711013345Z-6.cygnus.gnu-win32@kirin.continet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Original-To: "'gnu-win32@cygnus.com'" <gnu-win32@cygnus.com>
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63
Original-Sender: owner-gnu-win32@cygnus.com

It doesn't seem like tclsh uses the same naming convention as the rest
of the tools.  For example, I can do:  

	bash$ cat //e/foo/bar

and it works fine, but if I do:  

	bash$ tclsh76 //e/foo/bar

and it is a legit tcl file, then I get:  

	couldn't read file "//e/foo/bar": no such file or directory

but the following does work:  

	bash$ tclsh76 e:/foo/bar

Am I doing something wrong, or is this a bug.  If it's a bug, do you
think you might fix it soon?  

Thanks!
Colin Davey

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
