|
|
why???
Since Windows 95 it has been case sensitive. And there were extensions from third parties that allowed earlier versions do long file names and case sensitivity.
The one thing I dislike about OSX is that it is case insensitive. I would also like to know why you think the difference between MyDocument and mydocument is "annoying and confusing"? (Other than a bad naming convention).
why???
maybe your Windows 95 is case sensitive, but mine is not. Nor is my copy of Windows 2000 ('my documents' and 'My Documents' are the same place).
why???
mine is not. Nor is my copy of Windows 2000 ('my documents' and 'My Documents' are the same place) Um, "My Documents" and "my documents" being in the same place would make your copy of Windows case-sensitive. Confusing, huh?
What does case sensitive mean?
Sorry, I think you missed the point.
case-aware != case-sensitive
No. FAT and FAT32 filesystems (and NTFS, for that matter) are exactly like default HFS+: case-aware, but not case-sensitive. You cannot create two files, "FOO" and "Foo", in the same directory on any of these filesystems. Having a case-sensitive option for HFS+ is an absolute must-have for real OS X servers. It's also handy for those of us who like to layout CD-Rom images prior to burning. Some CDs I produce have directories like "index" in the same directory as a file named "INDEX". Have to build those on my BSD box. No, it is not an option to change the names of these files or directories. In this case the underlying system needs to change to support the workflow, not the other way around. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|