Mail Archives: cygwin/1997/07/10/20:38:55
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 AT cygnus DOT com" with one line of text: "help".
- Raw text -