From 31f82962a173c5f1e2eff2c340891833f58fa461 Mon Sep 17 00:00:00 2001 From: davidsb Date: Tue, 25 Jul 2000 20:49:59 +0000 Subject: [PATCH] Entry 'Are mixed-case filenames possible with Cygwin?': Expand slightly, add reference to coolview. --- winsup/doc/how.texinfo | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/winsup/doc/how.texinfo b/winsup/doc/how.texinfo index 4c06cece6f..dc65c87a47 100644 --- a/winsup/doc/how.texinfo +++ b/winsup/doc/how.texinfo @@ -360,9 +360,6 @@ filesystem so we can also access the files under Windows 9x. @subsection Are mixed-case filenames possible with Cygwin? -@strong{(Please note: This section has not yet been updated for the latest -net release.)} - Several Unix programs expect to be able to use to filenames spelled the same way, but with different case. A prime example of this is perl's configuration script, which wants @code{Makefile} and @@ -370,9 +367,14 @@ of this is perl's configuration script, which wants @code{Makefile} and just different case, so the configuration fails. In releases prior to beta 16, mount had a special mixed case option -which renamed files in such a way as to allow mixed case filenames. -We chose to remove the support when we rewrote the path handling -code for beta 16. +which renamed files in such a way as to allow mixed case filenames. We +chose to remove the support when we rewrote the path handling code for +beta 16. The standard Windows apps -- explorer.exe, +cmd.exe/command.com, etc. -- do not distinguish filenames that differed +only in case, resulting in some (very) undesirable behavior. + +Sergey Okhapkin had maintained a mixed-case patch ('coolview') until +about B20.1, but this has not been updated to recent versions of Cygwin. @subsection What about DOS special filenames? -- 2.11.0