diff options
author | David Starks-Browning <starksb@ebi.ac.uk> | 2002-03-20 23:14:30 +0000 |
---|---|---|
committer | David Starks-Browning <starksb@ebi.ac.uk> | 2002-03-20 23:14:30 +0000 |
commit | 3d27e4aaa5dff0d0d5b36f1b4f52bfcfad6898cb (patch) | |
tree | 88556c85f7161ac88622ee5912e232a3844a61f0 | |
parent | d5ded091b67c91367646d985ae870847de400458 (diff) | |
download | newlib-3d27e4aaa5dff0d0d5b36f1b4f52bfcfad6898cb.zip newlib-3d27e4aaa5dff0d0d5b36f1b4f52bfcfad6898cb.tar.gz newlib-3d27e4aaa5dff0d0d5b36f1b4f52bfcfad6898cb.tar.bz2 |
add "cygwish80.exe" to list of tcl/tk apps that do not understand paths
-rw-r--r-- | winsup/doc/how-using.texinfo | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/winsup/doc/how-using.texinfo b/winsup/doc/how-using.texinfo index 1ac751a..c714cb3 100644 --- a/winsup/doc/how-using.texinfo +++ b/winsup/doc/how-using.texinfo @@ -682,10 +682,10 @@ Perhaps that may be your problem? @subsection Why doesn't Cygwin tcl/tk understand Cygwin paths? -The versions of Tcl/Tk distributed with Cygwin (e.g. cygtclsh80.exe) are -not actually "Cygwin versions" of those tools. They are built with the -@samp{-mno-cygwin} option to @code{gcc}, which means they do not -understand Cygwin mounts or symbolic links. +The versions of Tcl/Tk distributed with Cygwin (e.g. cygtclsh80.exe, +cygwish80.exe) are not actually "Cygwin versions" of those tools. +They are built with the @samp{-mno-cygwin} option to @code{gcc}, which +means they do not understand Cygwin mounts or symbolic links. See the entry "How do I convert between Windows and UNIX paths?" elsewhere in this FAQ. |