ThePhD

Björkus "No time_t to Die" Dorkus

@ThePhD

Living disaster, ready to strike!

✨ Somehow Is A C Expert ✨ Smooches Unicode-kun 💕 Pixel Art is Cool 🎨 Banner by Bugurri and Avatar by KIING KIISMET ✨

log inask
ThePhD
@ThePhD
ThePhD
@ThePhD
ThePhD
@ThePhD

Not the MacOS + git Unicode Fail 😭

Using my git tool and realizing that they don't normalize the filenames in filepaths so after moving to MacOS with my git commits, everything that has an accent in it now claims it's a completely different file despite these files being committed literally YEARS ago 😭💀

I'm sorry but C and C++ software, plus the popular operating systems, are never beating the "dogshit at text" allegations.

Holy fuck!

ThePhD
@ThePhD

important daily affirmation

I will not make a patch for unicode path normalization to git as my patch will be rejected and I will be belitted by everyone who participates in the process

I will not make a patch for unicode path normalization to git as my patch will be rejected and I will be belitted by everyone who participates in the process

I will not make a patch for unicode path normalization to git as my patch will be rejected and I will be belitted by everyone who participates in the process

I will not make a patch for unicode path normalization to git as my patch will be rejected and I will be belitted by everyone who participates in the process

I will not make a patch for unicode path normalization to git as my patch will be rejected and I will be belitted by everyone who participates in the process

I will not make a patch for unicode path normalization to git as my patch will be rejected and I will be belitted by everyone who participates in the process

I will not make a patch for unicode path normalization to git as my patch will be rejected and I will be belitted by everyone who participates in the process

ThePhD
@ThePhD

core.precomposeunicode

Oh hey I don't have to. I was looking in "git attributes" for this, but I can solve this with:

git config core.precomposeunicode true

Thanks to a tip from tef!!

You must log in to comment.

in reply to @ThePhD's post:

dog
@dog

God, yeah. Git file names just being whatever + APFS’s very opinionated normalization is a rough combo :/

I think I mentioned this before but I’ve run into some interesting stuff with filesystem Unicode normalization in an app that needs to run cross platform + that doesn’t have access to Unicode normalization stuff internally

login to reply
jckarter
@jckarter

IIRC if you format a volume as “case sensitive APFS” then it will treat file names as a raw bag of bytes like a normal Unix system would. This of course breaks a lot of Mac software so you probably don’t want to format your primary volume that way, but worst case you could add a second case-sensitive volume and put a picky git checkout there

login to reply
dgelessus
@dgelessus

as a one-off solution, you can also create a small(ish) disk image formatted as case-insensitive, mount it, and clone the repo onto there. Though that only makes sense for repos that you use once/rarely. Otherwise, it's more convenient to create an extra volume on your real disk for that purpose, as you say (and with APFS containers, adding an extra volume is not very complicated or risky anyway).

login to reply