From: Lee Rothstein <lee@veritech.com>
To: "Cygwin, eMail List" <cygwin@Cygwin.com>
Subject: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
Date: Thu, 26 May 2011 18:29:00 -0000 [thread overview]
Message-ID: <4DDE9BE5.90105@veritech.com> (raw)
Issue: Possible confusing consequences of CYGWIN variable option:
glob:noignorecase
What follows is an edited transcript of my confusion about trying
to find the command "xwin" (and eventual resolution), having
forgotten about its capitalization. More specifically, I was
trying to figure out if it was a binary or a script (not having
used X in the last year, or so).
BTW, the reason I had glob:noignorecase set was to catch
capitalization errors on HTML file names I develop for a
LAMP server.
The transcript, however, indicates the option will not achieve my
aim.
--
/ $ cd /bin
/bin $ echo $CYGWIN
tty title nodosfilewarning glob:noignorecase winsymlinks ntsec
/bin $ type xwin
/bin/xwin
/bin $ which xwin
/bin/xwin
/bin $ ls -l xwin
-rwxrwx--- 1 lr root 2080270 Apr 22 14:45 xwin
/bin $ ls -l xwin*
-rwxr-xr-x 1 lr root 24590 Oct 14 2009 xwininfo.exe
-rwxr-xr-x 1 lr root 172544 Jan 19 2009 xwinwm.exe
# 'rwhich' is a case insensitive regex command finder script,
# I wrote, not a part of the Cygwin distribution
/bin $ rwhich $ rwhich xwin
/local/Scripts/start_xwin.old
/bin/dmxwininfo.exe
/bin/lyxwin.exe
/bin/startxwin.exe
/bin/XWin.exe
/bin/xwininfo.exe
/bin/xwinwm.exe
/bin $ ls -l XWin*
-rwxrwx--- 1 lr root 2080270 Apr 22 14:45 XWin.exe
/bin $ xwin
--
<Successfully starts X Windows>
--
And, yes, had I thought of it first, I could have used 'file':
/bin $ file xwin
xwin: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for
MS Windows
but the capitalization issue remains.
Finally, I am aware of the change that can be made to the
registry that will make the file system case sensitive, but I've
been burned in the past by non-standard changes to the registry,
and will avoid that.
BTW, it's little excursions like this that make me value Cygwin
more, not less. Creating the illusion of a coherent *NIX
environment on Windows is non-trivial. Thanks, Cygwin developers.
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2011-05-26 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 18:29 Lee Rothstein [this message]
2011-05-26 19:36 ` Christopher Faylor
2011-05-26 19:58 ` Lee D. Rothstein
2011-05-27 5:30 ` Corinna Vinschen
2011-05-27 15:53 ` File Name Case Sensitivity & Globbing! Was: " Lee D. Rothstein
2011-05-27 16:12 ` Corinna Vinschen
2011-05-27 17:39 ` Thorsten Kampe
2011-05-27 21:36 ` Edward McGuire
2011-05-27 22:46 ` Thorsten Kampe
2011-05-28 7:51 ` Corinna Vinschen
2011-05-28 19:03 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DDE9BE5.90105@veritech.com \
--to=lee@veritech.com \
--cc=cygwin@Cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).