Thread (152 messages) flat view 152 messages, 23 authors, 2016-06-15

Re: git on MacOSX and files with decomposed utf-8 file names

From: Wincent Colaiuta <hidden>
Date: 2016-06-15 22:44:06

El 17/1/2008, a las 5:08, Linus Torvalds escribió:
On Wed, 16 Jan 2008, Kevin Ballard wrote:
quoted
I believe it exists because HFS+ was created at a time when the Mac  
was moving
from a multi-encoding world (which was a nightmare) to a Unicode  
world and
they wanted to remove ambiguity in filenames. But I wasn't around  
when they
made this decision so this is just a guess.
I do agree. And I think starting out case-insensitive (something  
they must
really hate by now) also made it less of an issue.
I hope you're right (about them hating it), but we'll see. They've  
just opened the source for the ZFS port they're working on. By the  
time it goes final and becomes the default FS, replacing HFS+,  
probably within a couple of years, we'll see if they make the same two  
design decisions which cause the kinds of problems being discussed  
here (case-insensitivity, and ubiquitous FS-level UTF-8 normalization).

I've done a dumb search in the ZFS source code for "CASE" and see that  
it can in theory support case-insensitivity as an optional feature.  
The potential is there for Apple to use this. I personally hope that  
they don't, because as has already been pointed out, these little  
tricks tend to make life more difficult for users rather than helping  
them (the day I have two files in the same directory called "Märchen"  
and want to specify one of them on the command line I'll worry about  
that when I come to it).

http://fuzzy.wordpress.com/2007/06/09/zfsandfilesystemoptions/

Cheers,
Wincent
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help